This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-06-30
Channels
- # admin-announcements (19)
- # announcements (4)
- # beginners (22)
- # boot (76)
- # cider (92)
- # clojure (235)
- # clojure-berlin (3)
- # clojure-germany (1)
- # clojure-italy (8)
- # clojure-japan (18)
- # clojure-russia (26)
- # clojure-sg (1)
- # clojure-uk (25)
- # clojurescript (55)
- # code-reviews (7)
- # core-async (53)
- # datomic (13)
- # euroclojure (63)
- # jobs (39)
- # ldnclj (45)
- # off-topic (9)
- # om (7)
- # onyx (6)
- # reading-clojure (1)
- # reagent (5)
- # yada (22)
Would you like to have a peek at my attempt to cut the helper functions in liberator into more general use libraries? I’d push something alpha-ish then.
yes definitley
woke up this morning, found a bug in Ring.,..: https://github.com/ring-clojure/ring/issues/212
(or at least I think it's a bug)
Wow. That’s a hot topic. I think URI encoding has been debated for ages Amazon uses encoding sniffing which pretty clever:
Note the embedded „ÅMÅŽÕÑ“ string (lost by percent encoding)
oh dear, I didn't want to wake the dead on this one
is URI encoding really that controversial?
It’s a valid use case to query with non-ASCII values. What do you suggest else? I would not necessarily adhere to the request content-type but in the end you need use the acutal charset the browser sent.
This might be of interest: http://stackoverflow.com/questions/140549/what-character-set-should-i-assume-the-encoded-characters-in-a-url-to-be-in
it's quite rare that you use 'query' parameters when sending content, but still valid
I might want to google myself and my name is Müller.
The above SO post point to RFC 2396
> For original character sequences that contain non-ASCII characters, however, the situation is more difficult. Internet protocols that transmit octet sequences intended to represent character sequences are expected to provide some way of identifying the charset used, if there might be more than one [RFC2277]. However, there is currently no provision within the generic URI syntax to accomplish this identification. An individual URI scheme may require a single charset, define a default charset, or provide a way to indicate the charset used.
Ok, sorry for the noise: here we go: RFC3987 IRIs: http://tools.ietf.org/html/rfc3987
Hahaha: "If the IRI is written on paper, read aloud, …“ made my day.
Another link for the readling list on that topic: http://www.w3.org/International/articles/idn-and-iri/
HTML5 is pretty clear on how to submit and parse form data with query strings: http://www.w3.org/TR/html5/forms.html#application/x-www-form-urlencoded-encoding-algorithm