On Wed, 24 Aug 2005, Andrei Zmievski wrote: > I took a closer look at this today and RFC 2616 does not specify > whether user agents are supposed to send a charset parameter in the > Content-Type header of the POST request. I did not see any of my > browsers doing so. I think we can safely disregard this and rely on > http_input_encoding and output_encoding settings. We are not going to > use Accept-Charset for the reasons you mention.
I don't know if this is useful, but Sam Ruby did a bunch of digging into HTTP/HTML/XML encodings and precedence rules. See this presentation -- Slides 72 - 75. (Note link below starts at slide 72.) http://intertwingly.net/slides/2005/etcon/72.html If possible, I would prefer not to assume that we only need to follow the behavior of popular user agents. Someone could be using PHP as a web service server and have people write client scripts submitting all kinds of POST data that needs to be processed correctly. In an ideal world (heh), PHP would handle all of those scripts as long as they followed the specifications. -adam -- [EMAIL PROTECTED] | http://www.trachtenberg.com author of o'reilly's "upgrading to php 5" and "php cookbook" avoid the holiday rush, buy your copies today! -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
