Re:Apple.com currently has a self-signed certificate (fixed ...
by roghummal on Monday October 20, 2014 @04:56PM
(#8484438)
https://apple.com does redirect to https://www.apple.com, but it does so with an Apple-issued certificate. Are you running Chrome on OS X?
If you use curl/wget/similar on a machine that doesn’t have Apple’s certificates installed the 301 fails (bad cert).
"curl: (60) Peer certificate cannot be authenticated with known CA certificates”
Oddly, when I first tried to load https://apple.com inside Vienna (OS X RSS reader) it refused to load (bad cert), now it loads fine. Hmmm.
Re:Apple.com currently has a self-signed certificate (fixed ...
by dekz on Monday October 20, 2014 @05:10PM
(#8484514)
I am using Chrome on OSX and do not get it:
Re:Apple.com currently has a self-signed certificate (fixed ...
by jrochkind1 on Monday October 20, 2014 @09:03PM
(#8485413)
I too am using Chrome on OSX.
Different root CA's?
Re:Apple.com currently has a self-signed certificate (fixed ...
by quonn on Monday October 20, 2014 @04:07PM
(#8484205)
Strange, but someone else saw it, too. Maybe they have fixed it on some of their servers.
Re:Apple.com currently has a self-signed certificate (fixed ...
by jackweirdy on Monday October 20, 2014 @04:48PM
(#8484401)
+1 I only get it without the www; chrome doesn't let me redirect away either
Ah wait, are you only getting it on "https://apple.com"? In my Chrome browser, that immediately redirects to www.apple.com -- but if the first one was self-signed, wouldn't it be untrusted by the browser, and wouldn't the browser refuse to redirect and give me a warning instead?
Confused as to if I'm seeing the same thing as you or not.