Hi Andrea,

I have done some further investigation using curl based on you clue
about the gzipping.

In fact the binary stuff we see has been double gzipped! using the
ReverseProxyFilter=true.
With the ReverseProxyFilter=false there is no issue as there is just 1 gzip
and the browser duly displays it correctly.

I have raised a ticket on Jira describing this in more detail and with some curl
commands to reproduce and verify the issue.

See http://jira.codehaus.org/browse/GEOS-4756.

This could be a relatively simple fix in the Geoserver code. Hopefully
its simply
a matter of finding where the second gzip is happening and removing
it.

Cheers,

Andrew


---------- Forwarded message ----------
From: Andrew Walsh <[email protected]>
Date: Thu, 8 Sep 2011 09:53:12 +1000
Subject: Re: [Geoserver-users] Reverse Proxy Filter bug with 2.1.1?
To: Andrea Aime <[email protected]>
Cc: Geoserver-users <[email protected]>

Hi Andrea,

Thanks for your quick reply and advice.
I will raise a ticket on JIRA. Using Apache mod_proxy_html
certainly seems a feasible alternative. I had a short read about how
to use it and it looks quite technical/detailed. It would help me
a lot if you could show me a copy of the settings you used
in your Apache httpd.conf.

You noted later that:

"PS: The caps binary issue seems to be related to an interaction
between proxy, servlet proxy and gzip compression filter,
as if I use curl without enabling gzip compression I get back
the caps document properly."

Does that mean the binary output we are getting is gzipped?
Could you send me the URL that you used with Curl.

Thanks,

Andrew

On 9/7/11, Andrea Aime <[email protected]> wrote:
> On Wed, Sep 7, 2011 at 7:29 AM, Andrew Walsh <[email protected]> wrote:
>> Hi Users and Developers,
>>
>> We recently installed Geoserver 2.1.1 from .war file on our
>> Tomcat. We run our Geoserver behind a reverse proxy setting
>> the PROXY_BASE_URL through the "global settings" web form and
>> switching on the 'Reverse Proxy Filter' to true in the
>> WEB-INF/web.xml. Apache 2.2 at the front end does a proxy to
>> our Tomcat/geoserver at the back end. We found that that this setup
>> worked fine with our previous Geoserver 2.0.1 but now we get
>> the following problems with 2.1.1:-
>>
>> 1) Output from the GetCapabilities requests to WMS 1.1.1 and WFS 1.1.0
>> produces binary garbage.
>>
>> 2) GML and CSV output for all layers produces binary garbage.
>>
>> Other things like WMS getMap drawing and getFeatureInfo seem to be
>>
>> workingfine still as they were with 2.0.1
>>
>> I note that when I set the Reverse Proxy Filter to 'false' the problems
>> with the GetCap. and GML/CSV XML output go away. Hence my theory that
>> problem is related to the use of the Reverse Proxy filtering. However
>> we can't use that as a workaround as we need the Reverse Proxy
>> filter switched on to correctly filter URL's in within html output coming
>> back to the client outside the front end.
>
> The servlet filter was put in a hidden place because, theoretically at
> least,
> a reverse proxy should be able to do the changes in the returned html
> itself.
> Apache mod-proxy has a filter module that does exactly that, on my Linux
> system the package is:
>
> libapache2-mod-proxy-html - Apache2 filter module for HTML links rewriting
>
> So I don't have a direct insight in what the issue with the servlet filter
> might
> be, and I invite you to open a ticket on jira.codehaus.org, but the above
> might be an alternative solution.
>
> Cheers
> Andrea
>
> --
> -------------------------------------------------------
> Ing. Andrea Aime
> GeoSolutions S.A.S.
> Tech lead
>
> Via Poggio alle Viti 1187
> 55054  Massarosa (LU)
> Italy
>
> phone: +39 0584 962313
> fax:      +39 0584 962313
>
> http://www.geo-solutions.it
> http://geo-solutions.blogspot.com/
> http://www.youtube.com/user/GeoSolutionsIT
> http://www.linkedin.com/in/andreaaime
> http://twitter.com/geowolf
>
> -------------------------------------------------------
>

------------------------------------------------------------------------------
Doing More with Less: The Next Generation Virtual Desktop 
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops?   How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to