Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

HTTP2 bug. Error wher making POST request after HTTP2 timeout

  • 1 个回答
  • 7 人有此问题
  • 3 次查看
  • 最后回复者为 philipp

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.

被采纳的解决方案

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.

定位到答案原位置 👍 0

所有回复 (1)

more options

选择的解决方案

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.