1 |
On 03/18/2015 06:06 PM, Fernando Rodriguez wrote: |
2 |
> On Wednesday, March 18, 2015 4:41:25 PM walt wrote: |
3 |
>> On 03/17/2015 04:49 PM, walt wrote: |
4 |
>>> I get a certificate verification error when visiting https://www.att.com |
5 |
>>> using firefox-36.0, but not when using chrome-41.0.2272.76. |
6 |
>> |
7 |
>> Thanks to all who replied. I'm surprised by the variety of different results |
8 |
>> you reported. |
9 |
>> |
10 |
>> (BTW, I'm running firefox-bin-36.0, so the behavior may be a bit different |
11 |
> from |
12 |
>> the gentoo build.) |
13 |
>> |
14 |
>> FF will not even show me the secure att.com webpage. I get an entire html |
15 |
> page |
16 |
>> with this (very big) error message: |
17 |
>> |
18 |
>> Secure Connection Failed |
19 |
>> |
20 |
>> An error occurred during a connection to www.att.com. The OCSP server |
21 |
> experienced |
22 |
>> an internal error. (Error code: sec_error_ocsp_server_error) |
23 |
>> |
24 |
>> The page you are trying to view cannot be shown because the authenticity of |
25 |
> the |
26 |
>> received data could not be verified. |
27 |
>> |
28 |
>> Please contact the website owners to inform them of this problem. |
29 |
>> |
30 |
>> |
31 |
> |
32 |
> That sounds more like a networking issue. Are you behind a firewall? Is it |
33 |
> possible that you somehow blocked their OCSP server? Can you bypass the |
34 |
> firewall for testing? |
35 |
|
36 |
Wow, creepy. I forced a warm reboot of my home wireless router and the problem |
37 |
went away. I now see the gray triangle with the ! and I have no idea how long |
38 |
ago that started. I probably just didn't notice it until this router screw-up |
39 |
happened. And I don't even want to think about why my home router suddenly |
40 |
changed behavior :( |