Re: Tomcat 8.5.27 HTTP/2 connector not supporting GZIP compression

> On Jan 29, 2018, at 1:27 PM, Christopher Schultz > wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Pierre, > > On 1/29/18 1:07 PM, Pierre Chiu wrote: >> Here is the request/response header. You can tell >> Content-Encoding:gzip is missing

Re: Tomcat 8.5.27 HTTP/2 connector not supporting GZIP compression

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Pierre, On 1/29/18 1:07 PM, Pierre Chiu wrote: > Here is the request/response header. You can tell > Content-Encoding:gzip is missing when http2 is enabled. > > > > General (same with/without http2) Request > URL:https://x.ca/tomcat.css

Re: Tomcat 8.5.27 HTTP/2 connector not supporting GZIP compression

Hi Christopher, Here is the request/response header. You can tell Content-Encoding:gzip is missing when http2 is enabled. General (same with/without http2) Request URL:https://x.ca/tomcat.css Request Method:GET Status Code:200 Remote Address:198.163.180.42:443 Referrer

Re: capturing response output in filter

On Mon, Jan 29, 2018 at 9:27 AM, Mark Thomas wrote: > > On 29/01/18 17:19, Robert J. Carr wrote: > > I have a Filter that uses the output stream from the response of the > > servlet in the chain. In order to do this I create a custom response > > wrapper that has a custom

Re: capturing response output in filter

On 29/01/18 17:19, Robert J. Carr wrote: > I have a Filter that uses the output stream from the response of the > servlet in the chain. In order to do this I create a custom response > wrapper that has a custom servlet output stream. > > This works fine, but in moving to a newer Java EE API

capturing response output in filter

I have a Filter that uses the output stream from the response of the servlet in the chain. In order to do this I create a custom response wrapper that has a custom servlet output stream. This works fine, but in moving to a newer Java EE API there have been a couple new (abstract) methods added

Re: Tomcat 8.5.27 HTTP/2 connector not supporting GZIP compression

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Pierre, On 1/29/18 7:03 AM, Pierre Chiu wrote: > According to the change log, this is fixed in in bug 60276. > However, I cannot make it work. > > Gzip compression working fine without the UpgradeProtocol tag. > Adding UpgradeProtocol for http2

Re: Server returns different size of the resource

On 29/01/18 10:01, Charith Paranaliyanage wrote: > Hi All, > > I am running a web application using spring 4 in tomcat 8.5.8. There were > few errors in the log for "response has already been committed". These were > recorded for both spring controller urls and for some resources. > > One

Tomcat 8.5.27 HTTP/2 connector not supporting GZIP compression

According to the change log, this is fixed in in bug 60276. However, I cannot make it work. Gzip compression working fine without the UpgradeProtocol tag. Adding UpgradeProtocol for http2 and gzip compression stop working.

Server returns different size of the resource

Hi All, I am running a web application using spring 4 in tomcat 8.5.8. There were few errors in the log for "response has already been committed". These were recorded for both spring controller urls and for some resources. One exception as follows 2018-01-26 09:25:54 ERROR