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

Avatar for Username

搜索 | 用户支持

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

详细了解

话题已存档。 如果需要帮助请提出新问题。

Can't access https site

  • 1 个回答
  • 1 人有此问题
  • 20 次查看
  • 最后回复者为 Shadow110

fredcwbr
fredcwbr
more options

Howdy,

I can't acess https://webveic.ccbfinanceira.com.br/ ONLY WITH FIREFOX (45+ or 56+) ; receiving a message of interrupted when loading.

Using wireshark, found that after CONNECTION ESTABLISHED 200 OK --> firefox starts a SSL HELLO CLIENT , instead of a TLSv1 HELLO CLIENT.,

Did compare using Google-Chrome 62.0.3202.75 ,,


Follows PERTINENT TCP transcript of FIREFOX conversation::

30 2.942425470 192.168.32.44 192.168.33.185 HTTP 295 CONNECT webveic.ccbfinanceira.com.br:443 HTTP/1.1 32 2.982720472 192.168.33.185 192.168.32.44 HTTP 105 HTTP/1.1 200 Connection established 34 2.982993132 192.168.32.44 192.168.33.185 SSL 270 Client Hello 35 2.983180166 192.168.33.185 192.168.32.44 TCP 66 3128 → 36563 [ACK] Seq=40 Ack=434 Win=31104 Len=0 TSval=521130987 TSecr=3129245 36 3.024289382 192.168.33.185 192.168.32.44 TCP 66 3128 → 36563 [FIN, ACK] Seq=40 Ack=434 Win=31104 Len=0 TSval=521130997 TSecr=3129245 37 3.024579222 192.168.32.44 192.168.33.185 TCP 66 36563 → 3128 [FIN, ACK] Seq=434 Ack=41 Win=29312 Len=0 TSval=3129256 TSecr=521130997

    • Connection is closed here...


And the same transcript using google-chrome . ,

13 1.416390182 192.168.32.44 192.168.33.185 HTTP 307 CONNECT webveic.ccbfinanceira.com.br:443 HTTP/1.1 25 1.494568301 192.168.33.185 192.168.32.44 HTTP 105 HTTP/1.1 200 Connection established 27 1.494942928 192.168.32.44 192.168.33.185 TLSv1 282 Client Hello 60 1.620670604 192.168.33.185 192.168.32.44 TLSv1 322 Server Hello, Certificate, Server Key Exchange, Server Hello Done


Could anyone advice??

Howdy, I can't acess https://webveic.ccbfinanceira.com.br/ ONLY WITH FIREFOX (45+ or 56+) ; receiving a message of interrupted when loading. Using wireshark, found that after CONNECTION ESTABLISHED 200 OK --> firefox starts a SSL HELLO CLIENT , instead of a TLSv1 HELLO CLIENT., Did compare using Google-Chrome 62.0.3202.75 ,, Follows PERTINENT TCP transcript of FIREFOX conversation:: 30 2.942425470 192.168.32.44 192.168.33.185 HTTP 295 CONNECT webveic.ccbfinanceira.com.br:443 HTTP/1.1 32 2.982720472 192.168.33.185 192.168.32.44 HTTP 105 HTTP/1.1 200 Connection established 34 2.982993132 192.168.32.44 192.168.33.185 SSL 270 Client Hello 35 2.983180166 192.168.33.185 192.168.32.44 TCP 66 3128 → 36563 [ACK] Seq=40 Ack=434 Win=31104 Len=0 TSval=521130987 TSecr=3129245 36 3.024289382 192.168.33.185 192.168.32.44 TCP 66 3128 → 36563 [FIN, ACK] Seq=40 Ack=434 Win=31104 Len=0 TSval=521130997 TSecr=3129245 37 3.024579222 192.168.32.44 192.168.33.185 TCP 66 36563 → 3128 [FIN, ACK] Seq=434 Ack=41 Win=29312 Len=0 TSval=3129256 TSecr=521130997 ** Connection is closed here... And the same transcript using google-chrome . , 13 1.416390182 192.168.32.44 192.168.33.185 HTTP 307 CONNECT webveic.ccbfinanceira.com.br:443 HTTP/1.1 25 1.494568301 192.168.33.185 192.168.32.44 HTTP 105 HTTP/1.1 200 Connection established 27 1.494942928 192.168.32.44 192.168.33.185 TLSv1 282 Client Hello 60 1.620670604 192.168.33.185 192.168.32.44 TLSv1 322 Server Hello, Certificate, Server Key Exchange, Server Hello Done Could anyone advice??

所有回复 (1)

Shadow110
Shadow110
more options

Possibly file a bug report. https://bugzilla.mozilla.org/ Detail the issue as you did and if have more info the better.