Avatar for Username

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

이 쓰레드는 보존되었습니다. 만약 도움이 필요하시면 새로운 질문을 올려주세요.

Can't access https site

  • 1 답장
  • 1 이 문제를 만남
  • 114 보기
  • 최종 답변자: 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.