I've searched the mailing list and bugzilla, and it looks like this was
addressed in Tomcat 4.1.30, but I still see a problem with 4.1.30. Remy in
his comments mentioned it's probably a configuration issue (and hinted some
actual test/data would be useful). Here is what I did:
1) Clean install of Tomcat 4.1.30 standalone running on port 80.
2) Copied over test.jsp (attached) into the ROOT directory of tomcat.
3) Used CURL to get the server response.
Test.jsp:
++++++++++++++++++
<%
response.setContentType("application/pdf");
%>
<html>
<head>
<title>
Worked?
</title>
<body>
Charset test
</body>
</html>
+++++++++++++++++++
cURL response (using org.apache.coyote.tomcat4.CoyoteConnector):
+++++++++++++++++++
HTTP/1.1 200 OK
Set-Cookie: JSESSIONID=24F976F993E84090BFC69EC9E77A8710; Path=/
Content-Type: application/pdf;charset=ISO-8859-1
Content-Length: 90
Date: Wed, 12 May 2004 21:34:57 GMT
Server: Apache-Coyote/1.1
cURL response (using org.apache.catalina.connector.http.HttpConnector):
+++++++++++++++++++++++
HTTP/1.1 200 OK
Content-Type: application/pdf;charset=ISO-8859-1
Date: Wed, 12 May 2004 21:46:25 GMT
Server: Apache Tomcat/4.1.30 (HTTP/1.1 Connector)
Transfer-Encoding: chunked
Set-Cookie: JSESSIONID=65AABE61AA1C86FDF963B459D67D1573; Path=/
It looks like charset is still being set, which is wrong. Any ideas? Is the
jsp file incorrect?
Thanks.
