-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace leftover joomla.org (and subdomains) HTTP links for HTTPS links (where possible) #8791
Replace leftover joomla.org (and subdomains) HTTP links for HTTPS links (where possible) #8791
Conversation
@andrepereiradasilva regarding cdn see first post of joomla/joomla-websites#20 |
For help.joomla.org the help screen proxy (/proxy on that subdomain) On Saturday, December 26, 2015, andrepereiradasilva <
|
@mbabker
I think those can also be changed to HTTPS without issues. Do you agree? |
Yes those can change. On Saturday, December 26, 2015, andrepereiradasilva <
|
@@ -140,8 +140,8 @@ | |||
'Joomla Translations' => 'http://community.joomla.org/translations.html', | |||
'Joomla Resources' => 'http://resources.joomla.org/', | |||
'Community Portal' => 'http://community.joomla.org/', | |||
'Security Center' => 'http://developer.joomla.org/security.html', | |||
'Developer Resources' => 'http://developer.joomla.org/', | |||
'Security Center' => 'https://developer.joomla.org/security.html', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should actually be Security Centre
and linking to https://developer.joomla.org/security-centre.html
. Not 100% related to this PR but this particular test has been failing for some time if it's comparing links and text.
As for the test case involving |
@mbabker thanks for your comments Made the two changes and travis accepted them without problems. We also have the By the way, the certificate is incorrect in that domain. |
Looking at this patch and specially the tests/unit/stubs/database/...
|
It's PHP's behavior actually... http://php.net/manual/en/function.serialize.php
|
Thanks Michael. |
Ok. So all fine. |
closed as comments above, new PR will be made. |
Description
An year after #5478, this PR is for normalize the joomla.org URI in Joomla code to use HTTPS.
In this PR all joomla.org domains (and subdomains) in joomla code were checked, and then checked if those serve in HTTP, HTTP and HTTPS or exclusively HTTPS (HTTP redirect to HTTPS).
For the ones that the change seems possible without issues (certificate errors, protocols errors, redirects to HTTP, mixed content, etc) the change is done in this PR.
Please note this is not a blind search -> replace.
List of joomla.org domains (found in code and completly https with this PR)
List of joomla.org domains (found in code but will have to wait for a future PR)
Other domain in code
There are other domains used only for Unit tests to simulate errors but doesn't really exist or are only used in unit tests, so those were not changed:
How to test
Check the "Files changed" in this PR and verify the changes.
More info
For checking the domains that exist in Joomla code it was used several
egrep
linux commands:egrep -R 'joomla\.org' /path/to/joomla/
egrep -R 'http:(//|\\/\\/|\\\\/\\\\/)subdomain\.joomla\.org' /path/to/joomla/
egrep -R 'https:(//|\\/\\/|\\\\/\\\\/)subdomain\.joomla\.org' /path/to/joomla/
See joomla/joomla-websites#20 for a list of Joomla domains and the HTTP to HTTPS site conversion process.
Suggestions or corrections are welcome.