Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

daily.tmr.js.org #2855

Merged
merged 4 commits into from Mar 7, 2019

Conversation

Projects
None yet
3 participants
@ttttmr
Copy link
Contributor

ttttmr commented Mar 6, 2019

Can I add this domain name, it seems that I have not used such a four-level domain name?

tmr.js.org -> web: ttttmr.github.io
daily.tmr.js.org -> web: ttttmr.github.io/daily

Thanks.

@ttttmr

This comment has been minimized.

Copy link
Contributor Author

ttttmr commented Mar 6, 2019

And there is a question, where should should be placed in daily.tmr, I put it in front of tmr.js.org

ttttmr and others added some commits Mar 6, 2019

@MattIPv4
Copy link
Collaborator

MattIPv4 left a comment

Commit valid, CNAME present, site appears to have content *

* based off https://github.com/ttttmr/daily

@MattIPv4 MattIPv4 changed the title add daily.tmr.js.org daily.tmr.js.org Mar 6, 2019

@indus

This comment has been minimized.

Copy link
Member

indus commented Mar 6, 2019

There is no way for me to provide SSL for second level subdomains. Nevertheless I've added it to JS.ORGs zonefile: http://daily.tmr.js.org
Could you please add a comment behind your record in the list "// noCF" to declare I've informed you of this issue.

@ttttmr

This comment has been minimized.

Copy link
Contributor Author

ttttmr commented Mar 7, 2019

Ok, I added the noCF comment, thanks.

@MattIPv4

This comment has been minimized.

Copy link
Collaborator

MattIPv4 commented Mar 7, 2019

@indus Should be good to go now

@indus

This comment has been minimized.

Copy link
Member

indus commented Mar 7, 2019

Welcome https://daily.tmr.js.org
(A request to http://daily.tmr.js.org gets redirected to HTTPS a valid response is given. I'm not sure how this is enforced because any processing by Cloudflare is turned off?!?)

@indus indus merged commit 9a09eb6 into js-org:master Mar 7, 2019

@MattIPv4

This comment has been minimized.

Copy link
Collaborator

MattIPv4 commented Mar 7, 2019

@indus I would guess the https is being handled by Cloudflare and the SSL cert is from them. All git.io pages get SSL for them, but normally the Cf proxy replaces that with the Cf ssl.

@indus

This comment has been minimized.

Copy link
Member

indus commented Mar 7, 2019

😕 @MattIPv4 but this was not always the case. I would guess this has changed with: https://github.blog/2018-05-01-github-pages-custom-domains-https/
Good to know, that this is kind of incorrect now:

There is no way for me to provide SSL for second level subdomains.

But it is still necessary disable the CF proxy.

@ttttmr

This comment has been minimized.

Copy link
Contributor Author

ttttmr commented Mar 8, 2019

I also feel confused, I found that it can not be redirected to HTTPS, but the Enforce HTTPS option can be checked, then I checked up, it works, before it is not optional, say

Unavailable for your site Because your domain is not properly configured to support HTTPS

Now use the certificate of Let's Encrypt instead of Cloudflare.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.