Hi Mark, It is a *direct connection* with no proxy or no reverse proxy or no load balancer in the middle. We have a web app (UI) that make backend call and return 204 with no content and send it to the browser. An interesting fact is very thing works on Chrome but not with firefox. We have tried everything and we looked tomcat code and we see a change log around this area.
It is hard to come up with a sample, but I will try it. I am just trying to give clue which code or line causing the problem to narrow down the issue, but it is not helping. Thanks, Bhavesh On Wed, Mar 8, 2023 at 11:43 AM Mark Thomas <ma...@apache.org> wrote: > On 08/03/2023 19:38, Bhavesh Mistry wrote: > > I will see if I can give a sample. But after removing JUST ONE LINE ( > > streamOutputBuffer.closed = true;) Everything seems to work. Somehow, > > firefox does not like an active stream being closed (I am not 100% what > > close does). > > > > I will try to work on a sample to reproduce this. I hope the above can > > give you some clue as to where the issue is. > > Wherever the issue is, it isn't with Tomcat and it isn't with Firefox. > I've tested them locally and they work correctly. > > Might you have a reverse proxy between Firefox and Tomcat? > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
