Hi, David, Colin, et al.,
| > Since I'm going to need support for chunked requests in 3.3 anyway, I'm
| > going ahead with the port of my 3.2.2 changes. I hope to have it in a
| > couple of days.
|
| The fix in Ajp13 ( java side ) should be already in, and any _small_
| fix in the java side is ok.
|
| Same for mod_jk, after a lot of review :-)
I had some reservations at some of the changes David presented, I think
the problem can be solved with a smaller code hit. Working on it now..
| > >- Does the java part need to know that the incoming data came in CHUNKED ?
| > The Java side can figure it out if the Content-Length is not set. Still,
| > the Content-Length might be set even when the transfer was chunked. Not
| > sure how much value would be added in knowing this explicitly.
I don't *think* the Java side needs to be changed at all, and Costin is right,
HTTP/1.1 s 4.4 says cl cannot be set with any non-identity transfer encoding.
| > >- Should we add others HTTP/1.1 commands like Range, Accept-Ranges, CONNECT
| > >?
| > I suppose these could be helpful but I haven't thought too much about it.
| > In general, it seems like a good idea to leverage as much as possible from
| > the transport.
Um, let's get chunked encoding in first...
Keith
