For some time now GeoServer has recognized the Content-Encoding header and applied gzip compression automatically, out of the box. It seems that GeoServer does not log about gzip compression being applied at any log level... But I have put together a jar with the extra logging; you can grab it from http://dev.opengeo.org/~dwinslow/gs-web-app-logging.jar . To use it:
1 - stop geoserver 2 - rename webapps/geoserver/WEB-INF/classes to webapps/geoserver/WEB-INF/classes_bk 3 - put the jar file in webapps/geoserver/WEB-INF/lib/ 4 - restart GeoServer and go to the Global Settings page. Set the logging level to VERBOSE. -- David Winslow OpenGeo - http://opengeo.org/ On Thu, Jan 6, 2011 at 7:49 PM, David Collins <[email protected]>wrote: > Thanks, David. > > That info is very helpful and makes this seem more achievable. > > Is there any documentation on setting this up and confirming that > compressed HTTP is being used between Geoservers? > Does/can this work with Jetty and Tomcat implementations of Geoserver? > I have only been able to find summary documentation on this option when > searching around. > > regards, > David > > > > On Fri, Jan 7, 2011 at 1:34 AM, David Winslow <[email protected]>wrote: > >> I'm not 100% sure, but I believe this option will activate gzip >> compression at the HTTP level, not the WFS level. In this case, it would be >> activated via an HTTP header and not a query parameter (see >> http://en.wikipedia.org/wiki/Gzip#Other_uses) >> >> Hope this helps. >> >> -- >> David Winslow >> OpenGeo - http://opengeo.org/ >> >> On Wed, Jan 5, 2011 at 8:02 PM, David Collins >> <[email protected]>wrote: >> >>> FYI, the problem disappeared when I deleted my layers and re-created them >>> - my layers now retrieve the data, both when the URL in the WFS Data Store >>> is .. >>> >>> >>> * >>> http://maitdevgi:8080/geoserver/wfs?service=WFS&version=1.0.0&request=GetCapabilities >>> * >>> or .. >>> *http://maitdevgi:8080/geoserver/wfs?service=WFS&request=GetCapabilities<http://maitdevgi:8080/geoserver/wfs?service=WFS&version=1.0.0&request=GetCapabilities> >>> * >>> >>> (The layers in the latter WFS data store display the data inverted in the >>> Open Layers preview, though.) >>> >>> The reason for doing this, though, was to try to have Geoserver #1 >>> getting data from Geoserver #2 using *zipped GML*. >>> >>> Although, I tick '*Use gzip encoding if server supports it*', the >>> requests on Geoserver #2 are always '*outputFormat = GML2*' for 1.0.0 >>> and '*outputFormat = text/xml; subtype=gml/3.1.1*' for 1.1.0. >>> >>> The 1.1.0 GetCapabilities includes GML2-GZIP, so I thought that this >>> should be requested .. >>> <ows:Parameter name="outputFormat"> >>> <ows:Value>text/xml; subtype=gml/3.1.1</ows:Value> >>> <ows:Value>GML2</ows:Value> >>> <ows:Value>GML2-GZIP</ows:Value> >>> <ows:Value>SHAPE-ZIP</ows:Value> >>> <ows:Value>csv</ows:Value> >>> <ows:Value>gml3</ows:Value> >>> <ows:Value>json</ows:Value> >>> <ows:Value>text/xml; subtype=gml/2.1.2</ows:Value> >>> </ows:Parameter> >>> >>> If you have used the TRY_GZIP option successfully, can you tell me where >>> I am going wrong? >>> >>> >>> >>> >
------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
