tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 40828] - non-working jsp example jsxp svg
Date Tue, 13 Feb 2007 10:40:30 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40828>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40828





------- Additional Comments From d.kennedy@lvnl.nl  2007-02-13 02:40 -------
Hi Mark,

Like you said I got het http headers and they are different between 5.5.20 en 
6.0.2.
In the response of 5.5.20 I see:
***************
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=53204A6840B839F56041E8810AE20EF9; Path=/duncan
Content-Type: image/svg-xml;charset=ISO-8859-1
Content-Length: 442
Date: Thu, 08 Feb 2007 14:57:23 GMT
***************
In the response of 6.0.2 I see:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=2C395C611F300A0C31AB255EBCE48555; Path=/duncan
Content-Type: image/svg-xml
Content-Length: 442
Date: Thu, 08 Feb 2007 14:58:31 GMT
****************
The only difference on first contact is the Content-Type.
There isn't a difference between the windows regional settings from the 2 
servers. So I looked at the internet to see some hits on this issue.
I couldn't find any accept links to the Coyote connector.
After downloading the source I found the difference in the response.java
This had been changed in the case of setting the character encoding:
reponse.java in Tomcat 5.5:
public PrintWriter getWriter() 
        throws IOException {
 
        if (usingOutputStream)
            throw new IllegalStateException
                (sm.getString("coyoteResponse.getWriter.ise"));
 
        /*
         * If the response's character encoding has not been specified as
         * described in <code>getCharacterEncoding</code> (i.e., the method
         * just returns the default value <code>ISO-8859-1</code>),
         * <code>getWriter</code> updates it to <code>ISO-8859-1</code>
         * (with the effect that a subsequent call to getContentType() will
         * include a charset=ISO-8859-1 component which will also be
         * reflected in the Content-Type response header, thereby satisfying
         * the Servlet spec requirement that containers must communicate the
         * character encoding used for the servlet response's writer to the
         * client).
         */
        setCharacterEncoding(getCharacterEncoding());
 
        usingWriter = true;
        outputBuffer.checkConverter();
        if (writer == null) {
            writer = new CoyoteWriter(outputBuffer);
        }
        return writer;
 
    }
 
response.java in Tomcat 6.0 rc2
public PrintWriter getWriter() 
        throws IOException {
 
        if (usingOutputStream)
            throw new IllegalStateException
                (sm.getString("coyoteResponse.getWriter.ise"));
 
        if (Globals.STRICT_SERVLET_COMPLIANCE) {
            /*
             * If the response's character encoding has not been specified as
             * described in <code>getCharacterEncoding</code> (i.e., the method
             * just returns the default value <code>ISO-8859-1</code>),
             * <code>getWriter</code> updates it to <code>ISO-8859-1</code>
             * (with the effect that a subsequent call to getContentType() will
             * include a charset=ISO-8859-1 component which will also be
             * reflected in the Content-Type response header, thereby satisfying
             * the Servlet spec requirement that containers must communicate the
             * character encoding used for the servlet response's writer to the
             * client).
             */
            setCharacterEncoding(getCharacterEncoding());
        }
 
        usingWriter = true;
        outputBuffer.checkConverter();
        if (writer == null) {
            writer = new CoyoteWriter(outputBuffer);
        }
        return writer;
 
    }
In 6.0.2 is an extra if and my idea is that this can cause the problem.
I really like to hear from you.
Regards,

Duncan Kennedy

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message