On Thu, 11 Sep 2003, John Cowan wrote: >> >> Obviously, we can't do that for GET(there's no C-T header for >> GET. Currently MS IE and Mozilla use a proprieatary '_charset_' for this >> purpose only when the hidden field of '_charset_' is present in the form). > > IMHO this should be documented and treated as best practice. Browsers should > not of course invoke a new charset unless they have to. In this way, the server > can recover from the garbling by treating what it gets as octets and doing its > own character decoding. Unfortunately this still doesn't cover the case where '_charset_' is _not_ mentioned in the form (since sending the parameter in that case may confuse the server). -- Ian Hickson )\._.,--....,'``. fL U+1047E /, _.. \ _\ ;`._ ,. http://index.hixie.ch/ `._.-(,_..'--(,_..'`-.;.'Received on Thursday, 11 September 2003 09:46:27 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 20 September 2007 14:34:16 GMT