Martin Holz wrote:
Hello,

several Testcases report a wrong Content-Type header,
because the charset is not handled. One example would be xmltestcases/functional/XML/multiplePutGets.xml.


<exceuteStep>
   <method>GET</method>
   <url>/slide/files/lock.xml</url>
   <headerErrors>
        <nonMatchingHeader name="Content-Type">
           <expectedValue>text/xml</expectedValue>
           <receivedValue>text/xml;charset=ISO-8859-1</receivedValue>
        </nonMatchingHeader>
   </headerErrors>
   <result>ERROR</result>
   <time>111</time>
</exceuteStep>

The response seems to be legal. Is it possible to change the test case,
so it accepts this response with and without charset?

Martin


Martin,


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.

Mike


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to