On Thursday 14 June 2001 23:40, Ged Haywood wrote:
> On Thu, 14 Jun 2001, Robin Berjon wrote:
> > The problem is simply that I need to mix that data with other data
> > in another encoding, which means I have to convert it.
>
> Do you send a charset specification to the client? This was often
> overlooked until the cross-site scripting thing blew up early last
> year. I wonder if browsers seeing that might be more forthcoming if
> they want to use a something different.
Yes I am, AxKit doesn't give you much of a choice there (rightfully so) :)
After doing a number of tests, I've found that browsers (even totally
non-compliant ones) tend to POST back in the same charset you used to send
the page to them, unless the user types characters that don't fit into that
charset (people usually post in the language in which the page is written,
but sometimes their names will not fit into the charset). The spec says they
_may_ do that if accept-charset is set to UNKNOWN (its default value), but
then the spec is moot when it comes to browsers.
So now if I could find a way to send UTF-8 to Netscape 4 without it blowing
up, I might have found a workable solution to this problem :-)
--
_______________________________________________________________________
Robin Berjon <[EMAIL PROTECTED]> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
"Chance is irrelevant. We will succeed."
-- 7o9
