2009/9/4 RPrager <ryan.pra...@gmail.com>: > > Here is the only difference I found in the Request Headers: > > FF2: Content-Type application/x-www-form-urlencoded > > FF3: Content-Type application/x-www-form-urlencoded; charset=UTF-8 > > Any ideas?
One definite possibility is that the server-side component is failing to cope with the (perfectly valid) inclusion of the charset information in the Content-Type request header. Check with the developer responsible that he isn't doing something silly like (in pseudo-code): if (Request.ContentType == "application/x-www-form-urlencoded") // then do the form parsing as this would cause the problem you are seeing, and is also a broken way of parsing a request. Regards, Nick. -- Nick Fitzsimons http://www.nickfitz.co.uk/
