On Sunday 03 March 2002 19:34, Tod Harter wrote: > > Right.... apart from that tiny little nagging problem being that the > > charset parameter on application/* is ILLEGAL. > > Perhaps... Anyway, the point is that "url-encoded" implies US-ASCII... Its > common for user agents to ignore that, but since there is no mechanism for > specifying the character set of a URL it is pretty much mandated. So if a > form is REALLY URL encoded, then it must be ASCII, mustn't it?
It ought to be, except that url-encoding can in fact encode any 8bit charset, which means that it can also take most of the iso-8859-* family. A number of browsers have that misbehaviour. > Well, I have yet to have a form submitted to me and I wasn't able to > process it. Doubtless it has happened somewhere to someone, but I've built > and deployed at a rough guess 40 web applications over the last 8 years. > Maybe I'm just lucky ;o). You're just lucky (or quite simply just working in english), it's happened to me many times over the past year. -- _______________________________________________________________________ Robin Berjon <[EMAIL PROTECTED]> -- CTO k n o w s c a p e : // venture knowledge agency www.knowscape.com ----------------------------------------------------------------------- To err is human, to purr feline. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
