[#6646] - [Improvement] - Status code 301 for Force SSL option
- Closed
- 4 Apr 2015
- Medium
- Build: staging
- # 6646
- Diff
- Kubik-Rubik:Improvement-Force-SSL-301-Status-Code
- Success The Travis CI build passed Details
User tests: Successful: Unsuccessful:
Changed status code for SSL redirects (Option: Force SSL in Global Configuration) to "301 Moved Permanently" as Google recommends it.
How to test
SSL has to be configured on your server to test this patch!
- Activate the option "Force SSL" in the Global Configuration (for Site and Administrator).
- Open the Developer Tools in your browser (usually button F12 in Windows)
Go to the frontpage and load the website manually with the scheme http:// (not https://) and check the status code on the tab "Network" in the developer tools.
Without the patch, you should see a 303 status code:
Apply patch with the help of the Patchtester component and check the status code again - 301
Do the same test for the backend!
See here for more details:
https://support.google.com/webmasters/answer/6073543
http://moz.com/blog/seo-tips-https-ssl
http://moz.com/learn/seo/redirection
joomla-cms-bot
- | Labels |
Added:
?
|
||
| Category | ⇒ | Libraries |
tested as described, test successful.
before patch 303, after patch 301.
Google is happy now... Thank you @Kubik-Rubik
| Labels |
Added:
?
|
||
| Status | Pending | ⇒ | Ready to Commit |
RTC 
Thanks!
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6646.
wilsonge
- | Status | Ready to Commit | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-04-04 12:40:14 |
| Labels |
Removed:
?
|
||
I tested it succesfully. Note that this is actually the first time I actually tested code. I tried to test using https://docs.joomla.org/Testing_Joomla!_patches/, but the patch tester did not seem to load (stuck on: Preparing to fetch GitHub data). Therefor I loaded the repository from https://github.com/joomla/joomla-cms and replaced the 2 changed files.
Before the test the code was a 303, after applying it was a 301, so test was executed succesfully.