Avatar for Username

Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

HTTP2 bug. Error wher making POST request after HTTP2 timeout

  • 1 răspuns
  • 7 au această problemă
  • 17 vizualizări
  • Ultimul răspuns de philipp

ddsmes
ddsmes
more options

I'm browsing site via HTTPS Site supports HTTP2. This is clear by FirefoxDebugger Site logs (i am admin) confirms my browser is using HTTP2 When I browse site via GET/HEAD requests - absolutely no problems. Site uses default HTTP2 timeout == 180secs This works. I open netstat|grep 443 and see after 3minutes that TCP connection to my client browser is closed. When I make GET request after timeout and closing TCP connection - all ok, connection is reestablished and new 180sec timeout is created. BUT (!!!) When I make POST request after timeout and connection closed - I have an "ERROR making secure connection to server". I have checked Chromium browser - they are ok, GET/POST requests does not generate errors after timeout. This is definitely FireFox bug.

I'm browsing site via HTTPS Site supports HTTP2. This is clear by FirefoxDebugger Site logs (i am admin) confirms my browser is using HTTP2 When I browse site via GET/HEAD requests - absolutely no problems. Site uses default HTTP2 timeout == 180secs This works. I open netstat|grep 443 and see after 3minutes that TCP connection to my client browser is closed. When I make GET request after timeout and closing TCP connection - all ok, connection is reestablished and new 180sec timeout is created. BUT (!!!) When I make POST request after timeout and connection closed - I have an "ERROR making secure connection to server". I have checked Chromium browser - they are ok, GET/POST requests does not generate errors after timeout. This is definitely FireFox bug.

Soluție aleasă

hello, this is a primarily community-run support forum so it's probably not the right place to report bugs (developers won't read here). if you want to file a bug, please do so directly at bugzilla.mozilla.org.

Citește acest răspuns în context 👍 0

Toate răspunsurile (1)

philipp
philipp
  • Moderator
more options

Soluție aleasă

hello, this is a primarily community-run support forum so it's probably not the right place to report bugs (developers won't read here). if you want to file a bug, please do so directly at bugzilla.mozilla.org.