tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 53112] Following asynchronous responses do not contain set response headers
Date Fri, 04 May 2012 11:48:18 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=53112

--- Comment #4 from Stig Runar Vangen <stig@vangen.org> ---
My original report might not have been too clear. I'll try to clearify a bit.
I've added two attachments to this bug, logs that describes how both Jetty and
Tomcat handles the same code for handling XMPP requests.

First off, with "request" I meant several blocks of communication back and
forth between the server and client in the same HTTP request. Using async
communication, it is possible to leave the connection open, and let the client
and server talk to eachother at any time. Between each communication block, the
request is "ended" as a normal request would be, using the content-length
header to determine where the request and response ends. This is supported by
both Tomcat and Jetty. The difference is that while Jetty correctly hands out
the headers you configure every single time, this only works for the first
block for Tomcat.

The request would work as follows:

* Client connects to server to servlet defined with async support
* Client sends first request as normal
* Server responds with content-length
* AsyncContext.dispatch()
* Client reads response, leaves connection open
* Client sends new "request" in the same manner as last time
* Server again responds with content-length
* AsyncContext.dispatch()
* Client reads response, leaves connection open
...

This is how I've understood that this should work, and this is how Jetty
currently does it. It might be that I'm wrong, so please correct me.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message