Re: Tomcat 9.0.72 Firefox issue with 204 response (Empty Body)

Hi, Mark and Tomcat team, Thank you for your support so far and I will take it up with Firefox. I will look into CSP as well. Thanks for checking this. Thanks, Bhavesh On Sat, Mar 18, 2023 at 4:56 AM Mark Thomas wrote: > That looks like a browser bug then. You'll need to raise that with

Re: Tomcat 9.0.72 Firefox issue with 204 response (Empty Body)

That looks like a browser bug then. You'll need to raise that with Firefox. Also, the CSP doesn't look quite right. "...form-action 'self'; https:;..." should probably be: "...form-action 'self' https:;..." Mark On 17/03/2023 23:34, Bhavesh Mistry wrote: Hi Tomcat Team and Mark, I am

Re: Tomcat 9.0.72 Firefox issue with 204 response (Empty Body)

Hi Tomcat Team and Mark, I am able to reproduce the problem with your sample app. *CSP large header is causing this problem we attached it to ALL responses. This custom header. I am not sure if this is a tomcat issue or Firefox. *We get *NS_ERROR_ABORT*. Sorry, it took a while but the issue

Re: Tomcat 9.0.72 Firefox issue with 204 response (Empty Body)

Hi Mark and Tomcat Team, We have been using tomcat 9 from version 0 to 70 and no issues so far with our application and firefox. We also tried to upgrade to 9.0.73, and show the same issue: As you can see from Devtools it is missing Protocol HTTP2 and is hung there. [image: image.png]

Re: Tomcat 9.0.72 Firefox issue with 204 response (Empty Body)

On 09/03/2023 18:19, Bhavesh Mistry wrote: Hi Mark, Your sample application worked 204 Firefox and our application does not work. That leads me to believe *Application Filter *is an issue. But should tomcat throw an exception if the response is already committed? A call to setStatus() after

Re: Tomcat 9.0.72 Firefox issue with 204 response (Empty Body)

Hi Mark, Your sample application worked 204 Firefox and our application does not work. That leads me to believe *Application Filter *is an issue. But should tomcat throw an exception if the response is already committed? I will try to see if I can reproduce it using a filter with the sample app

Re: Tomcat 9.0.72 Firefox issue with 204 response (Empty Body)

On 08/03/2023 21:32, Bhavesh Mistry wrote: Hi Mark, We have a NAT rule that forwards 443 to 8443. OK. That explains the change in port. Trust me on that, we have a direct connection. To rule out any networking layer issues, I did direct ssh -L 8443:localhost:8443 admin@10.40.207.140 and

Re: Tomcat 9.0.72 Firefox issue with 204 response (Empty Body)

Hi Mark, We have a NAT rule that forwards 443 to 8443. Trust me on that, we have a direct connection. To rule out any networking layer issues, I did direct ssh -L 8443:localhost:8443 admin@10.40.207.140 and created a tunnel (https://localhost:8443/) to bypass port 443. Yet, the issue is still

Re: Tomcat 9.0.72 Firefox issue with 204 response (Empty Body)

On 08/03/2023 19:52, Bhavesh Mistry wrote: 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

Re: Tomcat 9.0.72 Firefox issue with 204 response (Empty Body)

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

Re: Tomcat 9.0.72 Firefox issue with 204 response (Empty Body)

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

Re: Tomcat 9.0.72 Firefox issue with 204 response (Empty Body)

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

Re: Tomcat 9.0.72 Firefox issue with 204 response (Empty Body)

On 08/03/2023 19:05, Bhavesh Mistry wrote: *Then, *I build 9.0.72 src code *without HTTP2 no Content commit, and firefox worked ( I just replace tomcat-coyote.jar) . What is your suggestion we do next? * Again, if you can provide a simple test case (with source code - should be no more

Re: Tomcat 9.0.72 Firefox issue with 204 response (Empty Body)

Hi Mark and Chris, Thank you for your reply. We are using the latest version of* Firefox 110.1*. I have installed Live HTTP Header Live add-on and I see *NS_ERROR_ABORT and the request is stalled in the browser (the 204 status code is never shown in the Network tab). This applies to any

Re: Tomcat 9.0.72 Firefox issue with 204 response (Empty Body)

Bhavesh, On 3/7/23 22:07, Bhavesh Mistry wrote: Hi Mark Thomas and Tomcat Team, We have a strange issue with Tomcat 9.0.72.  All 204 response does not complete in firefox.  It works in the Chrome browser.  If we downgrade the tomcat version is less than .72. Everything works on all browsers.

Re: Tomcat 9.0.72 Firefox issue with 204 response (Empty Body)

On 08/03/2023 03:07, Bhavesh Mistry wrote: Hi Mark Thomas and Tomcat Team, We have a strange issue with Tomcat 9.0.72.  All 204 response does not complete in firefox.  It works in the Chrome browser.  If we downgrade the tomcat version is less than .72. Everything works on all browsers.

Tomcat 9.0.72 Firefox issue with 204 response (Empty Body)

Hi Mark Thomas and Tomcat Team, We have a strange issue with Tomcat 9.0.72. All 204 response does not complete in firefox. It works in the Chrome browser. If we downgrade the tomcat version is less than .72. Everything works on all browsers.