12 May
2006
12 May
'06
11:48 a.m.
John Bates wrote:
the header from laszlo for content-type was: "application/x-www-form-urlencoded;charset=UTF-8"
FYI, according to RFC 2616 HTTP/1.1, what follows Content-Type is:
type "/" subtype *( ";" attribute "=" value )
So if TBNL can't parse that, I's say it's a bug. They also seem to say that compliant HTTP/1.1 software should treat a missing charset parameter as ISO-8859-1, but I'm not sure.
Toby