4 ms·
Hmm, I don't seem to get that. While it seems unlikely, could you be getting MitM'ed? Ah wait, are you only getting it on "https://apple.com" https://apple.com
by jrochkind1 12y ago
Hmm, I don't seem to get that. While it seems unlikely, could you be getting MitM'ed?
Ah wait, are you only getting it on "https://apple.com" 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.
- quonn 12y agoStrange, but someone else saw it, too. Maybe they have fixed it on some of their servers.
- deleted 12y ago[deleted]
- jackweirdy 12y ago+1 I only get it without the www; chrome doesn't let me redirect away either
- roghummal 12y agohttps://apple.com https://apple.com does redirect to https://www.apple.com 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 https://apple.com inside Vienna (OS X RSS reader) it refused to load (bad cert), now it loads fine. Hmmm.
- dekz 12y agoI am using Chrome on OSX and do not get it: https://gist.github.com/dekz/7c911fa633e37fb130d4 https://gist.github.com/dekz/7c911fa633e37fb130d4
- jrochkind1 12y agoI too am using Chrome on OSX. Different root CA's?