Re: Empty Headers in response from Secure Websocket Upgrade request from Safari

2019-07-09 Thread Tom Kuo
Nevermind, i finally traced it all the way through the problem lies in the Spring Framework code. For anyone who happens to trip up on the same problem, our Spring is doing this in WebContentGenerator.applyCacheControl if (response.containsHeader(HEADER_EXPIRES)) { // Reset HTTP 1.0 Expires

Re: Empty Headers in response from Secure Websocket Upgrade request from Safari

2019-07-09 Thread Tom Kuo
> > I saw this both on 8.5.0.39 and 9.0.14 > Oh actually this was also present on the latest 8.5.42

Re: Empty Headers in response from Secure Websocket Upgrade request from Safari

2019-07-09 Thread Tom Kuo
> > Tomcat never sets "Cache-Control: no-store" and I can't find anywhere > where Tomcat sets an empty expire header either. > Looking through the code, I saw AuthenticatorBase set the Expires header if using security constraints and not disabledProxyCaching if it's not a POST request. We use

Tomcat 9 & Port 80

2019-07-09 Thread Arbelo, Ralph
Hello, I have Tomcat 9.0.21 installed (binary distribution) on an Ubuntu 16.04 server. My Java version is OpenJDK 11.0.4. I have the JSVC built and run the dameon.sh script to start and stop Tomcat via a systemd script. Everything works great, but now I need to run it on port 80 & 443. On our