Re: [Jolie-devel] HTTP charset behaviour

[Fabrizio M. <fam...@gm...>]

Sounds good! Shall we try discussing this on github as a request commit? I
like their Web gui for seeing diffs. :-)

Sent from my phone.
On Mar 16, 2015 8:58 AM, "Matthias Dieter Wallnöfer" <mwa...@ya...>
wrote:

> Yesterday I stumbled over another bug in our HTTP implementation which I
> would like to clarify here, so that you get an idea what is wrong:
>
> - in the HTTP extension we have this "charset" parameter, which at the
> moment we enforce for outgoing messages (perfectly correct) but also for
> incoming ones if no other charset has been specified.
>
> The latter behaviour is in clear contradiction to HTTP's RFC (
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.4.1) which
> enforces the use of latin1 (iso-8859-1) in that case.
>
> - I got across over this limitation only when setting our charset
> parameter testwise to "utf-16". The content gets delivered correctly, but
> webbrowsers like Firefox continue to send POST requests (form data in
> urlencoded) in URL-encoded ASCII (in theory also latin1 which is the
> superset).
>
> Attached the patch which makes us standard-conform and drops the charset
> parameter enforcement on inbound messages.
>
>
> Cheers,
> Matthias
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Jolie-devel mailing list
> Jol...@li...
> https://lists.sourceforge.net/lists/listinfo/jolie-devel
>
>