https://issues.apache.org/bugzilla/show_bug.cgi?id=53454
Christopher Schultz <ch...@christopherschultz.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
OS| |All
--- Comment #1 from Christopher Schultz <ch...@christopherschultz.net> ---
This is actually caused by the servlet API classes which are not a part of
Tomcat. Looking at servlet-api-2.5.jar, you can see this implementation of
HttpServlet.doHead:
protected void doHead(javax.servlet.http.HttpServletRequest,
javax.servlet.http.HttpServletResponse) throws
javax.servlet.ServletException, java.io.IOException;
Code:
0: new #11; //class javax/servlet/http/NoBodyResponse
3: dup
4: aload_2
5: invokespecial #12; //Method
javax/servlet/http/NoBodyResponse."<init>":(Ljavax/servlet/http/HttpServletResponse;)V
8: astore_3
9: aload_0
10: aload_1
11: aload_3
12: invokevirtual #13; //Method
doGet:(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)V
15: aload_3
16: invokevirtual #14; //Method
javax/servlet/http/NoBodyResponse.setContentLength:()V
19: return
That's roughly this Java code:
protected void doHead(HttpServletRequest req, HttpServletResponse resp)
throws ServletException, IOException
{
NoBodyResponse response = new NoBodyResponse(resp);
doGet(req, response);
response.setContentLength();
}
The NoBodyResponse class is a package-protected class whose setContentLength
method looks like this:
void setContentLength();
Code:
0: aload_0
1: getfield #5; //Field didSetContentLength:Z
4: ifne 18
7: aload_0
8: aload_0
9: getfield #4; //Field
noBody:Ljavax/servlet/http/NoBodyOutputStream;
12: invokevirtual #6; //Method
javax/servlet/http/NoBodyOutputStream.getContentLength:()I
15: invokespecial #7; //Method
javax/servlet/http/HttpServletResponseWrapper.setContentLength:(I)V
18: return
That's roughly this Java code:
void setContentLength()
{
if(!didSetContentLength)
super.setContentLength(noBody.getContentLength());
}
The field didSetContentLength is only set here:
public void setContentLength(int);
Code:
0: aload_0
1: iload_1
2: invokespecial #7; //Method
javax/servlet/http/HttpServletResponseWrapp
er.setContentLength:(I)V
5: aload_0
6: iconst_1
7: putfield #5; //Field didSetContentLength:Z
10: return
Which is this:
public void setContentLength(int len)
{
super.setContentLength(len);
didSetContentLength = true;
}
So, since you are not calling setContentLength(int), your Content-Length header
is being clobbered by the servlet API itself.
Try this instead:
resp.setContentLength(0);
resp.setHeader("Content-Length", String.valueOf(12345678900L));
I think that will get you around this particular oversight in the API classes.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
