On Sun, Jun 5, 2011 at 7:01 PM, William A. Rowe Jr. <wrowe@xxxxxxxxxxxxx> wrote: > you need to be more specific. > > HTTP 2.x has a filtering schema which applies -protocol- filters > after all -content-. ÂModules are presumed to generate content > unless they manipulate the filter stack. > > mod_proxy dechunks the backend response (it's entirely possible > for httpd to accept chunking, and the proxy client to not accept > it as HTTP/1.0), since T-E is a hop-by-hop header. > > So whatever *app server* you have that is chunking and not being > dechunked is an issue with the module you have receiving the > chunk response in httpd. ÂChunking is not part of the CGI spec, > therefore it's invalid input to mod_cgi[d]. ÂIt's completely > legitimate for mod_proxy_http. ÂTomcat has no such issues that > I'm aware of. > > So what app server are you talking about? I am testing this with Phusion Passenger and Unicorn. They are going to implement compression for chunked responses. That is, they are going to dechunk, compress, and chunk again, mod_deflate won't be involved for these responses. Is that what you'd expect to be needed? --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|