New issue 36 by fortescue: RequestProxy.java patch for type=proxy with
proxy target returning 'transfer-encoding: chunked'
http://code.google.com/p/urlrewritefilter/issues/detail?id=36
What steps will reproduce the problem?
1. setup rule that uses type="proxy"
2. setup proxy target that returns output as 'chunked' output. I used
geoserver. Use any geoserver setup.
3.
What is the expected output? What do you see instead?
When proxying the chunked response back to the requester, the data is
accumulated (probably incorrectly) rather than returned untouched. A
logically complete response is returned instead but the header
'transfer-encoding: chunked' is not removed from the response to the
requester. This randomly breaks images and Geoserver's map tiles.
I fixed this for my case (by removing the transfer-encoding header) but I'm
sure there are cases where the encoding should be preserved the chunks
returned mostly untouched. This fix will likely not help streaming
sources... Map tiles have a definitive end. I leave it to you to decide
what to do. I would at least appreciate the inclusion of this patch as
type=proxy is not usable for the quasi case now.
What version of the product are you using? On what operating system?
urlrewrite 3.2 on Linux/Windows with JBOSS 4.2.2.GA.
Please provide any additional information below.
This is key to moving GeoServer behind a proxy! Hopefully others can
benefit.
Attachments:
RequestProxy.java.patch 4.3 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
Comment #1 on issue 36 by tuckey: RequestProxy.java patch for type=proxy
with proxy target returning 'transfer-encoding: chunked'
http://code.google.com/p/urlrewritefilter/issues/detail?id=36
I'm applied this patch and it looks good, but in setupResponseHeaders
isChunked
always appears to be false? Is this correct?
Has this patched in the trunk code?
I came across this issue today while trying to pull a bunch of AJAX URLs
into the same domain. Solved it for my
environment by simply suppressing the transfer-encoding header in the
setupResponseHeaders method.
Attached is a smaller patch.
Attachments:
RequestProxy.patch 655 bytes