On September 12, 2019 2:19:30 PM UTC, Boris Petrov <bo...@profuzdigital.com> wrote: >Hi, > >I have two issues with the "default" Tomcat configuration (the only >thing I've changed from it is that I've added an `UpgradeProtocol` >directive and SSL certificates). Tomcat version is 9.0.24. > >The first one is the one I've written in the subject - for all 304 >responses Tomcat is adding a `Content-Length: 0` header. This happens >only on HTTP/2. Any suggestions how to debug this are appreciated.
That looks like a Tomcat bug. The flow for HTTP/2 is different to HTTP/1.1 and it looks like we missed a check. >The second issue is that Tomcat sets the same ETag header for a static >file that changes between updates of my WAR. That is, I have a file >called `git-revision.json` in which there is the build-date and the >revision-number of the application. This file changes with every new >release of our WAR. Note that the length of the file is always the >same. >And Tomcat *ALWAYS* puts the same ETag header for it - >`W/"89-318204000000"` (89 is the file length, not sure about the rest). It is the last modified timestamp. >Why is Tomcat not changing the ETag header? This breaks for clients >which have already loaded it and don't get the new version because 304 >is returned. If the file contents changes the expectation is that the timestamp changes too. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
