Avatar for Username

Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Learn More

Bu başlık arşivlendi. Yardıma ihtiyacınız varsa lütfen yeni bir soru sorun.

HTTP2 bug. Error wher making POST request after HTTP2 timeout

  • 1 yanıt
  • 7 kişi bu sorunu yaşıyor
  • 3 gösterim
  • Son yanıtı yazan: 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.

Seçilen çözüm

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.

Bu yanıtı konu içinde okuyun 👍 0

Tüm Yanıtlar (1)

philipp
philipp
  • Moderator
more options

Seçilen çözüm

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.