[
https://issues.apache.org/jira/browse/JENA-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355538#comment-15355538
]
Andy Seaborne commented on JENA-1200:
-------------------------------------
This applies to the whole standalone server.
We could choose to make it the default. I think the only reason it isn't in
Jetty/Tomcat normally, is that some files are already compressed. It can be
costly for serving simple files but query results are not simple files.
> Support gzip encoding for the Fuseki standalone server.
> -------------------------------------------------------
>
> Key: JENA-1200
> URL: https://issues.apache.org/jira/browse/JENA-1200
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Fuseki 2.4.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Fix For: Fuseki 2.4.1
>
>
> See
> http://stackoverflow.com/questions/38069760/how-do-i-make-fuseki-serve-gzipped-content
> From testing and code inspection, Fuseki2 does not provide gzip support. The
> command line argument {{--gzip}} doesn't do anything.
> It looks like any support was removed during upgrade to jetty9.? when the the
> way Gzip is handled chnaged. The Jetty GZipFilter is deprecated and is a
> no-op. It is replaced by the GZipHandler which works just fine.
> http://www.eclipse.org/jetty/documentation/9.4.x/gzip-filter.html
> We could load this in regardless of any configuration and make it available
> whenever a request uses {{Accept-Encoding: gzip}}.
> *WAR deployment, including Tomcat*
> Tomcat has a similar architecture - compression is not provided by some
> feature of the standard servlet/webapp web.xml but by configuring of the
> Tomcat HttpConnector.
> https://tomcat.apache.org/tomcat-8.0-doc/config/http.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
