当サイトはユーザー体験を改善するためのメンテナンスを実施中に機能が制限される予定です。記事を読んでもあなたの問題が解決せず質問をしたい場合は、Twitter の @FirefoxSupport、Reddit の /r/firefox で、サポートコミュニティが皆さんを助けようと待機しています。

Avatar for Username

Mozilla サポートの検索

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.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

SSL request size greater than 8K is giving connection reset error on Firefox 11

  • 2 件の返信
  • 20 人がこの問題に困っています
  • 28 回表示
  • 最後の返信者: cor-el

harihat
harihat
more options

we are currently facing an issue with Firefox 10 & 11. I am seeing the termination of SSL connection when the size of the post message is greater than 8K. This caused 'connection reset' errors on the browser side. I believe this is due to the beast attack fixes on FF10 and later version. The https works fine until the request size reaches 8600 bytes. The same issue didnt happen if i proxy the FF through fiddler.

we are currently facing an issue with Firefox 10 & 11. I am seeing the termination of SSL connection when the size of the post message is greater than 8K. This caused 'connection reset' errors on the browser side. I believe this is due to the beast attack fixes on FF10 and later version. The https works fine until the request size reaches 8600 bytes. The same issue didnt happen if i proxy the FF through fiddler.

すべての返信 (2)

ffxsf
ffxsf
more options

You should either use the Feedback tool or Bugzilla to report this to the developers:

https://input.mozilla.org/en-US/feedback https://bugzilla.mozilla.org/

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

The "The connection was reset" error message can be caused by a bug fix for the BEAST (Browser Exploit Against SSL/TLS) attack that the server doesn't handle.

See comment 60 in this bug report for workaround, but be aware that this makes you vulnerable to that BEAST attack.

  • bug 702111 - Servers intolerant to 1/n-1 record splitting. "The connection was reset"

Be sure to remove that environment variable after testing to prevent you from being vulnerable to that exploit.