Michael Smith <[EMAIL PROTECTED]> writes:
Though the charset is legal (the protocol permits it), it's incorrect in this case, I think - so the test shouldn't be changed.
If you're using a recent (latest?) version of tomcat 4.1.x, I think it's a newly introduced bug (judging from various reports on tomcat-dev). I believe it's been fixed in cvs, but not yet in a release. If you're NOT using tomcat, then I don't know what the cause of this is.
Yes, I am using Tomcat 4.1.29. Reading the reports from tomcat-dev, i am even more confused. The charset parameter is unnecessary, because
ISO-8859-1 is the default. It may also confuse some clients.
But why is it illegal?
In this case (because it's a text/* mime-type) it's not illegal. However, it IS incorrect - it's stating that the content is encoded using ISO-8859-1. It's not - I'm pretty sure it's UTF-8.
The best solution would be for slide to set the content type to include the _correct_ charset parameter. Leaving it out entirely is also perfectly acceptable.
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
