On 30/06/2022 07:40, Mark Thomas wrote:
<snip/>
I think I'm going to need the sample app to investigate this.
I have received the sample application and can recreate the issue.
Going back to your original summary:
<quote>
1) Main page was requested by Firefox from Tomcat (GET ...)
2) Tomcat sends the first compressed chunks of data to the browser
3) Firefox reads the first packages and notices, that additional
resources are needed (CSS, JS ...)
4) While Tomcat is still sending the main page in chunks, the browser is
already requesting additional resources on other channels
5) Firefox is sending a RST_STREAM and closes that last requested
stream(s) (dunno why it does request first and then closes the channel)
6) Tomcat is sending a GoAway message to the browser
7) Tomcat stops also sending the main page (on a different channel)
</quote>
I tested with 10.0.x.
I don't see the above sequence.
I ran the test 4 times, closing the browser between each test
When things go wrong it appears that FireFox is re-using the main page
(ticket.jsp) from a cache.
I see the additional resources being requested and then cancelled.
I do not see any GOAWAY messages from Tomcat.
I do see a single GOAWAY message from the browser to Tomcat when I close
the browser window (as expected).
I don't see anything going wrong on the Tomcat side.
At the moment, this looks to me like an issue with Firefox rather than
with Tomcat.
If you can narrow the test case to something that shows Tomcat doing
something wrong, then I'd be happy to look at this again.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
