Raise the Hammer
this blog entry has been updated
Update: as of February 6, 2012, RTH now uses its own dedicated SSL certificate.
Effective immediately, you can now access Raise the Hammer using the HTTP Secure protocol:
Note that the start of the URL is "https" instead of "http". HTTPS is a protocol that encrypts requests sent from the browser to the web server and web pages sent from the server back to the browser.
Because the communications are encrypted in an HTTPS connection, it is much more difficult for third parties to intercept and eavesdrop on your browsing activity, for example if you are using a shared public wifi network to access the internet. Tools like Firesheep demonstrate just how easy it is 'hijack' an unencrypted browser session on a public wifi network.
A few caveats:
RTH uses the security certificate of WebFaction, our hosting provider. That means you may get a scary warning when you try to connect to RTH via HTTPS saying that there is a mismatch between the website domain and the certificate. Depending on your browser, you will be prompted to accept the connection anyway and/or add an exception for this domain.
Update: As of February 2012, RTH uses its own SSL certificate (issued by StartCom) so you should no longer get scary warnings from your browser.
If you access RTH using HTTPS, all the content - web pages, style sheets, javascript files, images, etc. - on the RTH web server will be served in HTTPS. However, some pages also include content from third party sites - like embedded images and media files - that are served in plain HTTP. On those pages, your browser will probably warn you that you have requested an encrypted page that contains both encrypted and unencrypted files.
Because all communications between your browser and the web server are encrypted on an HTTPS connection, page loading will be a bit slower than it is on an unencrypted HTTP connection.
This change is part of our ongoing efforts to make your use of RTH more secure.
Update: updated to note that RTH now uses its own SSL certificate, not WebFaction's certificate.
By MattM (registered) | Posted March 17, 2011 at 11:21:22
Looks good, thanks Ryan.
By MattM (registered) | Posted March 17, 2011 at 11:25:56
Little note, for some reason the site keeps switching back to http. I think it happens after I submit a post. Happened twice now. Using IE 7/Windows Vista.
Edit: Confirmed, it happens as soon as I submit a post.
Comment edited by MattM on 2011-03-17 11:29:02
By Undustrial (registered) - website | Posted March 17, 2011 at 17:29:11
Woot! I've been looking into HTTPS a bunch lately. Really rad stuff.
By TnT (registered) | Posted March 19, 2011 at 18:43:28
Perhaps unrelated, but I've been having trouble posting of late getting "Internal Server Error."
By markstone (registered) | Posted June 15, 2019 at 09:21:31
Hypertext Transfer Protocol Secure is an augmentation of the Hypertext Transfer Protocol. It is utilized for secure correspondence over a PC arrange and is generally utilized on the Internet. In HTTPS, the correspondence convention is encoded utilizing Transport Layer Security, or, once in the past, it's antecedent, Secure Sockets Layer. https://www.hireessaywriter.com/essay-wr...
You must be logged in to comment.
There are no upcoming events right now.
Why not post one?