GitHub pages (or Fastly on their behalf) is doing that redirection for me. Unfortunately, it doesn’t serve a cert for my apex, so I don’t think there’s anything I can do myself.
-
-
Replying to @derekprior @schneems and
Update: I decided to take the plunge and tell GitHub pages to enforce TLS, and this makes GitHub Pages/Fastly handle the redirection appropriately. I had been holding off on that hoping to verify all the pieces worked first so as not to upset my dozens of users/month, but YOLO.
2 replies 0 retweets 1 like -
Replying to @derekprior @schneems and
Seems wrong. https://prioritized.net/ => SSL error
2 replies 0 retweets 0 likes -
Replying to @calebthompson
Not here. Possible DNS propagation? All these check out for me: `http://prioritized.net ` `http://prioritized.net `, `https://prioritized.net `. All redirect to `www` on HTTPS with no cert errors in the chain.
3 replies 0 retweets 0 likes -
Replying to @derekprior
So HTTPS on the apex is still giving a cert error. Seems to be serving GitHub’s certificate. Non-ssl works as it did yesterday, redirecting to www.
1 reply 0 retweets 0 likes -
Replying to @calebthompson
Hmm. Yeah, I see it now as well. Any ideas on what I should do here? Seems a pretty big oversight on google pages support to say nothing of this…
1 reply 0 retweets 0 likes -
-
Replying to @derekprior
Yes, you'll have to yes, you'll have to use the apex as your domain yes
2 replies 0 retweets 0 likes -
Replying to @calebthompson @derekprior
My watch transcribed this and didn’t run it by me before sending.
1 reply 0 retweets 1 like -
You'll have to yes
4:20 PM - 12 May 2018
0 replies
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.