chore: ensure https on fsfe link text #1477

Manually merged
FSFE merged 1 commits from nico.rikken/fsfe-website:feature/convert-absolute-links-18-manual into master 2020-07-03 09:36:15 +00:00
Member

This PR ensures https:// on fsfe links (as link or in text) and removes the www. subdomain. Relates to issue #1378

Executed commands:

find . -iname '*.xhtml'  -exec perl -pi -e 's/http:\/\/(www\.)?fsfe\.org/https:\/\/fsfe\.org/g' {} \;
find . -iname '*.xml'  -exec perl -pi -e 's/http:\/\/(www\.)?fsfe\.org/https:\/\/fsfe\.org/g' {} \;
find . -iname '*.svg'  -exec perl -pi -e 's/http:\/\/(www\.)?fsfe\.org/https:\/\/fsfe\.org/g' {} \;
find . -iname '*.php'  -exec perl -pi -e 's/http:\/\/(www\.)?fsfe\.org/https:\/\/fsfe\.org/g' {} \;
find . -iname '*.txt'  -exec perl -pi -e 's/http:\/\/(www\.)?fsfe\.org/https:\/\/fsfe\.org/g' {} \;
This PR ensures `https://` on fsfe links (as link or in text) and removes the `www.` subdomain. Relates to issue #1378 Executed commands: ``` find . -iname '*.xhtml' -exec perl -pi -e 's/http:\/\/(www\.)?fsfe\.org/https:\/\/fsfe\.org/g' {} \; find . -iname '*.xml' -exec perl -pi -e 's/http:\/\/(www\.)?fsfe\.org/https:\/\/fsfe\.org/g' {} \; find . -iname '*.svg' -exec perl -pi -e 's/http:\/\/(www\.)?fsfe\.org/https:\/\/fsfe\.org/g' {} \; find . -iname '*.php' -exec perl -pi -e 's/http:\/\/(www\.)?fsfe\.org/https:\/\/fsfe\.org/g' {} \; find . -iname '*.txt' -exec perl -pi -e 's/http:\/\/(www\.)?fsfe\.org/https:\/\/fsfe\.org/g' {} \; ```
Owner

Could you please rebase? There are some conflicts due to the merge of #1464

Could you please rebase? There are some conflicts due to the merge of #1464
Author
Member

Thanks, no problem. I've rebased it. All these changes are starting to show its effect, less and less issues in the codebase 😄

Thanks, no problem. I've rebased it. All these changes are starting to show its effect, less and less issues in the codebase :smile:
Author
Member

I've now included other filetypes that seem harmless. I can do the same replacement on the .pl and .xsl files, but that might have unintended consequences so I've decided to not do that yet.

I've now included other filetypes that seem harmless. I can do the same replacement on the `.pl` and `.xsl` files, but that might have unintended consequences so I've decided to not do that yet.
Owner

Thanks! I couldn't think of a scenario in which pl and xsl actually would create problems, but as you say in German: "the devil is a squirrel" :D

Thanks! I couldn't think of a scenario in which pl and xsl actually would create problems, but as you say in German: "the devil is a squirrel" :D
FSFE closed this pull request 2020-07-03 09:36:15 +00:00
Sign in to join this conversation.
No description provided.