Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Docs on enforcing HTTPS and avoiding mixed content #33017

Merged
merged 2 commits into from Feb 9, 2021
Merged

Docs on enforcing HTTPS and avoiding mixed content #33017

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6d2519e
Docs on enforcing HTTPS and avoiding mixed content
philipkiely Feb 8, 2021
f6861aa
Merge branch 'main' into docs-v5-optimizations-https
XhmikosR Feb 9, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 4 additions & 2 deletions site/content/docs/5.0/customize/optimize.md
View file
Open in desktop
Expand Up @@ -74,6 +74,8 @@ Whenever possible, be sure to compress all the code you serve to your visitors.

_Help wanted with this section, please consider opening a PR. Thanks!_

## Always use https
## Always use HTTPS

_Help wanted with this section, please consider opening a PR. Thanks!_
Your website should only be available over HTTPS connections in production. HTTPS improves the security, privacy, and availability of all sites, and [there is no such thing as non-sensitive web traffic](https://https.cio.gov/everything/). The steps to configure your website to be served exclusively over HTTPS vary widely depending on your architecture and web hosting provider, and thus are beyond the scope of these docs.

Sites served over HTTPS should also access all stylesheets, scripts, and other assets over HTTPS connections. Otherwise, you'll be sending users [mixed active content](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content), leading to potential vulnerabilities where a site can be compromised by altering a dependency. This can lead to security issues and in-browser warnings displayed to users. Whether you're getting Bootstrap from a CDN or serving it yourself, ensure that you only access it over HTTPS connections.