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=40056>.
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=40056

           Summary: added httpHeader after invoking chain.doFilter(..) gets
                    lost by chunked transfer
           Product: Tomcat 5
           Version: 5.5.7
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P4
         Component: Unknown
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: [EMAIL PROTECTED]


Normally, an added http-header AFTER the call "chain.doFilter(request, response)
" is not transmitted to the client if a servlet or subsequent filter closes the 
output stream. 
It IS transmitted, if the filter closes the stream itself using a wrapper 
perventing subsequent filters or the servlet from closing the  stream.

If the entity size increases above the max. HTTP-Package size the container 
automatically adds the header "transfer-encoding:chunked" and removes the 
"content-size" header.
In this case any header added AFTER the call "chain.doFilter(request, 
response)" 
is NOT transmitted any more.

{
            chain.doFilter(request, wrappedResponse);
            
            wrappedResponse.addHeader("Test-Header","not transmitted if 
chunked");
            
            // close Stream (call override-method of wrapper for ".close()")
            wrappedResponse.closeOutputStream();
}

soo many words 4 discribing a tiny bug...

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to