-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin Bialasinski wrote: > I tried quoted printable but had no luck, but it might be just me. It's useless to try encoding HTTP headers in any way, as no HTTP spec (rfc2616, rfc1945, erratas, etc) specify any encoding to be necessary.
More than that, I already described that Gecko parses headers correctly (nsHttp module), it's just some other part of their toolkit that messes with those headers before letting JS using them. :( > And there is also the question how the various browsers handle this. OK, here's a quick test: Mozilla Firefox 1.5.0.7 (Gecko/20060913) - Fail Mozilla Firefox 2.0b2 (Gecko/20060821) - Fail Mozilla SeaMonkey 1.0.5 (Gecko/20060910) - Fail Internet Explorer 6 - OK Opera 9.01 - Fail (Gecko-like) Konqueror 3.5.4 - Fail (Gecko-like) - -- Marius Feraru -----BEGIN PGP SIGNATURE----- iD8DBQFFEXIetZHp/AYZiNkRAqORAKDwqKYqE+nVZdgLGMAmM1RGhBd6TgCgmUnz YSAsICxWLJhnG0tOuaiPvgw= =BxY0 -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs -~----------~----~----~----~------~----~------~--~---
