Closed Bug 1006697 Opened 11 years ago Closed 11 years ago

redirect https to http on training.webmakerprototypes.org

Categories

(Webmaker Graveyard :: Training, defect)

Product:
Webmaker Graveyard
Component:
Training
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: laura, Assigned: johns)

Details

(Whiteboard: [training][june13])

Or vice versa, just need both of them to work! http://training.webmakerprototypes.org/en/ https://training.webmakerprototypes.org/en/ <-- craps out
marking critical cause we're blasting people (I double checked and I used http in the email blast, but just in case anyone else hits it)
Severity: normal → critical
When are people being blasted?
all this week
I've subbed a ticket to get SSL setup here.
The verification went through (thanks jbuck!), just waiting on MoCo to click "Approve" now.
We are unable to approve this cert... I believe it's because WHOIS for the domain is Jon Buckley, not Mozilla Foundation or Mozilla Corporation. We can't issue certs for domains we don't own. :) Best bet is probably to either transfer the domain (which may not be doable if it was only recently purchased- there's a waiting period), or perhaps :jbuck can supply a cert directly.
D'oh. Yeah, I can't see how I'm able to change my WHOIS info for that domain w/o changing the WHOIS for all my registered domains. I think we have to wait until later this month to transfer webmakerprototypes.org to Mozilla.. I can't seem to find that bug anymore though.
On May 20th we'll be able to transfer the domain, if my email archives are to be trusted. I'm opening a bug on you jbuck to generate a transfer code. Laura, can we hold until Tuesday or Wednesday to send? If we can wait until Tuesday or Wednesday to send, I'll 1) Get the whois moved over with jbuck's transfer code on May 20th 2) Get an SSL cert procured for training.webmakerprototypes.org from Digicert,and get on IRC to nudge the approval along. 3) I'll rehost this site on Cloudfront and make the appropriate bucket, CF, and DNS changes. 4) Send an email to folks who interact with webmakerprototypes.org about the new bucket, redo their IAM creds Laura, all, if Wednesday is not acceptable for this, we can use Brett's card to purchase a SSL cert on the Jbuck account before it is transferred, and do the same thing. My preference would be to wait the two days so we can manage these all in Digicert, but I understand if we need to move faster. (Note, I cannot setup an SSL-->non SSL redirect without an SSL cert first)
Flags: needinfo?(laura)
sure! no worries, wait til Wed.
Flags: needinfo?(laura)
Whiteboard: [training]
Whiteboard: [training] → [training][may30]
Assignee: nobody → jon
Assignee: jon → johns
Resubmitted our SSL request to be a SAN cert, waiting for approval on it.
Status: NEW → ASSIGNED
any news on this one jp?
Flags: needinfo?(johns)
We've got the SSL cert, it'll be up there in an hour or so. Working on a badgekit issue atm, then I'll update this.
SSL has been updated on Cloudfront, and I have a new distribution building. It will be at: d2k617z19fpfp2.cloudfront.net Now this means that moving forward, if we push new code or pages up, we'll likely need to have someone clear the CDN cache. I can train people on doing this as well as take care of such requests myself. After this finishes pushing to all edge servers, we'll test it and then move DNS to this (and forward http to https)
I am testing this now. To help me test, do this: 1) open your /etc/hosts file (use vi or emacs or text editor) Add this line at the bottom: 54.230.91.223 training.webmakerprototypes.org 2) in a fresh browser (incognito in chrome, private browsing in firefox, reset safari), test https://training.webmakerprototypes.org
Flags: needinfo?(matt)
Flags: needinfo?(laura)
Flags: needinfo?(johns)
Why not take advantage of the CDN invalidation features that s3_website already offers? https://github.com/laurilehmijoki/s3_website#using-your-existing-cloudfront-distribution
Very nice find jbuck!! Testing this right now with cache time set to 0s, the Modules button/dropdown does not work for me.
I notice if I go to https://d2k617z19fpfp2.cloudfront.net/en/exploring/resources/# it shows the menu under modules instead of a drop down.
Um...I don't know what you want me to do here. dunno where etc/hosts might be to help you test.
Flags: needinfo?(laura)
@ JP? What's next for this ticket?
Flags: needinfo?(matt) → needinfo?(johns)
Whiteboard: [training][may30] → [training][june13]
If we can get folks to test the site and possibly fix the modules drop down, we can use https for prod. https://d2k617z19fpfp2.cloudfront.net
Flags: needinfo?(johns)
Matt - can we ask one of our devs to look at and/or fix that drop down? P2PU was only contracted until June 1st. I have merge capabilities: https://github.com/p2pu/school-of-webmaking
Flags: needinfo?(matt)
@ JP: are you able to help here? Or suggest someone else who can?
Flags: needinfo?(matt) → needinfo?(johns)
I'm afraid I don't know much about front end stuff. We can probably ask Kate or Aki?
Flags: needinfo?(johns)
@ Laura: can you ask your P2PU contact to do it for us as a favor? (It's a busy week.) * If not let me know and we'll see who we can put on it.
Flags: needinfo?(laura)
:laura - I think the only fix you need to do is change https://github.com/p2pu/school-of-webmaking/blob/gh-pages/_layouts/base.html#L40 from an http:// script to an https:// script
k - will fix tomorrow JBuck :) Thanks!
Flags: needinfo?(laura)
hrm, ok I did that: https://github.com/p2pu/school-of-webmaking/commit/b8fb599ee61aefbea4b1727b3559e1d2cd1df7e7 But it doesn't work. Other ideas?
Flags: needinfo?(jon)
:laura there is a delay while the CDN updates content from the source website, and in that time period it got the new layout and it looks like everything is working the same on both sites now. :jp - want to flip the switch on this?
Flags: needinfo?(jon)
I just flipped DNS for this, so the https version should start serving shortly. Please note that since this is now on a CDN, changes you push up to the bucket will either: 1) Take hours to propagate and thus you will see the unchanged site/assets for some time after making a change in the bucket OR 2) We'll coordinate (contact jbuck or jp) to invalidate the CDN and pull new content. Even this takes ~15 minutes typically.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
I added a patch to see if we can do this automatically: https://github.com/p2pu/school-of-webmaking/pull/164
You need to log in before you can comment on or make changes to this bug.