https://issues.apache.org/bugzilla/show_bug.cgi?id=53112
Bug #: 53112
Summary: Following asynchronous responses do not contain set
response headers
Product: Tomcat 7
Version: 7.0.25
Platform: PC
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
AssignedTo: dev@tomcat.apache.org
ReportedBy: s...@vangen.org
Classification: Unclassified
This problem is related to this issue:
https://issues.apache.org/bugzilla/show_bug.cgi?id=50753
The first asynchronous request lets you set the response header, and that
response gets parsed correctly on the client side. The following requests in
the same async context does not let you set the response headers, and Tomcat
seem to give some default headers only. In addition, it also switches to
chunked transfer encoding because of missing content length. This results in
errors in clients trying to read the response from a Tomcat context. These
problems does not occur when using Jetty using the same Servlet 3.0 API's.
This problem was discovered while updating the BOSH plugin for the Vysper
project:
https://issues.apache.org/jira/browse/VYSPER-307
The same problem was observed in both Tomcat version 7.0.25 and 7.0.27.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- 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
