Redirecting jenkins.io to www.jenkins.io

10 views
Skip to first unread message

Olblak

unread,
Apr 21, 2020, 12:44:33 PM4/21/20
to 'Gavin Mogan' via Jenkins Infrastructure
Hi, 
I would like to switch jenkins.io website from apex domain to www.jenkins.io.
The main motivation is to use Fastly to proxy www.jenkins.io using a CNAME record from www to dualstack.d.sni.global.fastly.net. (which also support IPV6).

Another motivation is to be able to enable HSTS on the website.
Any objection? I opened the PR here

Slide

unread,
Apr 21, 2020, 2:07:04 PM4/21/20
to jenkin...@googlegroups.com
Would this remove the ability to go to "jenkins.io"? I think most people don't use www. prefix anymore. It may catch some people by surprise if this is the case.

--
You received this message because you are subscribed to the Google Groups "Jenkins Infrastructure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkins-infr...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/jenkins-infra/dd02bd41-50f1-450e-8664-f4692ae354a4%40www.fastmail.com.


--
Website: http://earl-of-code.com

Gavin Mogan

unread,
Apr 21, 2020, 2:09:19 PM4/21/20
to Jenkins Infrastructure
The PR redirects people from jenkins.io to www.jenkins.io

That'll make the very first landing of jenkins.io slower, but every page hit after that faster as they'll stay on www.jenkins.io

If its done with a permanent redirect (I need to check now), it'll update search results too.

Gavin

To view this discussion on the web, visit https://groups.google.com/d/msgid/jenkins-infra/CAPiUgVeFBN-2mJnJNQeiibCqfj1HPdfsfLeA12QkruPLsKRL1Q%40mail.gmail.com.

Olblak

unread,
Apr 22, 2020, 3:51:09 AM4/22/20
to 'Gavin Mogan' via Jenkins Infrastructure
Exactly we keep the website on jenkins.io but then we are redirected to www.jenkins.io which will be faster.
The search results will directly use www.jenkins.io.

This a pretty common pattern and better than having the website only on the apex domain

Slide

unread,
Apr 22, 2020, 9:00:38 AM4/22/20
to jenkin...@googlegroups.com
+1 then

To view this discussion on the web, visit https://groups.google.com/d/msgid/jenkins-infra/e8d38232-cf89-4e1e-8f01-b66c2992856a%40www.fastmail.com.

Mark Waite

unread,
Apr 23, 2020, 8:13:50 PM4/23/20
to Jenkins Infrastructure
+1 from me as well, though I'm still not clear how that will work with all the references on jenkins.io that refer to https://jenkins.io.  Won't they cause references back to the apex domain and thus defeat the content delivery network caching?


On Wednesday, April 22, 2020 at 7:00:38 AM UTC-6, Slide wrote:
+1 then

On Wed, Apr 22, 2020, 00:51 Olblak <gm...@olblak.com> wrote:
Exactly we keep the website on jenkins.io but then we are redirected to www.jenkins.io which will be faster.
The search results will directly use www.jenkins.io.

This a pretty common pattern and better than having the website only on the apex domain

On Tue, Apr 21, 2020, at 8:09 PM, 'Gavin Mogan' via Jenkins Infrastructure wrote:
The PR redirects people from jenkins.io to www.jenkins.io

That'll make the very first landing of jenkins.io slower, but every page hit after that faster as they'll stay on www.jenkins.io

If its done with a permanent redirect (I need to check now), it'll update search results too.

Gavin

On Tue, Apr 21, 2020 at 11:07 AM Slide <slid...@gmail.com> wrote:
Would this remove the ability to go to "jenkins.io"? I think most people don't use www. prefix anymore. It may catch some people by surprise if this is the case.

On Tue, Apr 21, 2020 at 9:44 AM Olblak <m...@olblak.com> wrote:

Hi, 
I would like to switch jenkins.io website from apex domain to www.jenkins.io.
The main motivation is to use Fastly to proxy www.jenkins.io using a CNAME record from www to dualstack.d.sni.global.fastly.net. (which also support IPV6).

Another motivation is to be able to enable HSTS on the website.
Any objection? I opened the PR here


--
You received this message because you are subscribed to the Google Groups "Jenkins Infrastructure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkin...@googlegroups.com.


--


--
You received this message because you are subscribed to the Google Groups "Jenkins Infrastructure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkin...@googlegroups.com.


--
You received this message because you are subscribed to the Google Groups "Jenkins Infrastructure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkin...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Infrastructure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkin...@googlegroups.com.

Marky Jackson

unread,
Apr 23, 2020, 8:44:27 PM4/23/20
to jenkin...@googlegroups.com
+1 from me

On Apr 23, 2020, at 5:13 PM, Mark Waite <mark.ea...@gmail.com> wrote:


To unsubscribe from this group and stop receiving emails from it, send an email to jenkins-infr...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/jenkins-infra/f34916b2-36dd-4062-b57b-a1661fa9faca%40googlegroups.com.

Olblak

unread,
Apr 24, 2020, 3:12:57 AM4/24/20
to 'Gavin Mogan' via Jenkins Infrastructure
+1 from me as well, though I'm still not clear how that will work with all the references on jenkins.io that refer to https://jenkins.io.  Won't they cause references back to the apex domain and thus defeat the content delivery network caching?

As long as jenkins.io creates references to jenkins.io (for js, css,etc.) and not www.jenkins.io, we won't be able to redirect jenkins.io to www.jenkins.io


Once validated we can enforce www.jenkins.io with this parameter

Considering that we have a consensus here, I am going to merge the pull request, anyway in the current state both www.jenkins.io and jenkins.io will work
Reply all
Reply to author
Forward
0 new messages