![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Moving to HTTPS
Sep. 16th, 2016 10:26 pmToday we switched postjobfree.com to https.
Now all pages are served over HTTPS, and if user requests http page - we redirect user to https://www.postjobfree.com/
Because all PostJobFree public pages are now secure, Google Chrome gives us "green lock" icon:
The reason to stop supporting legacy HTTP why we finally decided to make
This Google Blog article was the final nudge to switch from supporting both HTTP and HTTPS to "HTTPS-only" mode:
---
https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html
Beginning in January 2017 (Chrome 56), we’ll mark HTTP sites that transmit passwords or credit cards as non-secure, as part of a long-term plan to mark all HTTP sites as non-secure.
---
We still support HTTP requests for some legacy feeds and APIs, but even that may stop in a couple of years.
Now all pages are served over HTTPS, and if user requests http page - we redirect user to https://www.postjobfree.com/
Because all PostJobFree public pages are now secure, Google Chrome gives us "green lock" icon:
The reason to stop supporting legacy HTTP why we finally decided to make
This Google Blog article was the final nudge to switch from supporting both HTTP and HTTPS to "HTTPS-only" mode:
---
https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html
Beginning in January 2017 (Chrome 56), we’ll mark HTTP sites that transmit passwords or credit cards as non-secure, as part of a long-term plan to mark all HTTP sites as non-secure.
---
We still support HTTP requests for some legacy feeds and APIs, but even that may stop in a couple of years.
