2009/9/10 Karl Hungus <coldnebraskab...@googlemail.com>: > > I can see the form data in the body of the post too, using both Live > HTTP Headers and Charles. Which I guess only confuses me more. :-) > > One thing I did notice, is the Content-Type attribute of the request > header has "application/x-www-form-urlencoded; charset=UTF-8" for FF3, > but only "application/x-www-form-urlencoded" for FF2. I wondered if > that difference might be causing something strange to happen at the > server end. >
If the server developer (or the library being used on the server) is matching on the precise ContentType "application/x-www-form-urlencoded" (without the charset specifier) as a way of determining whether or not to parse the request body, then that is a bug: section 14.17 of RFC 2616 <http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.17> makes it clear that the version sent by FF3 is a valid form of the header. Regards, Nick. -- Nick Fitzsimons http://www.nickfitz.co.uk/
