Skip to content

Update guide.md to clarify redirect requirements - #224

Merged
konklone merged 2 commits into
masterfrom
redirect-clarity
Jan 16, 2017
Merged

konklone merged 2 commits into
masterfrom
redirect-clarity

Conversation

@h-m-f-t

@h-m-f-t h-m-f-t commented Jan 16, 2017

Copy link
Copy Markdown
Contributor

Several federal agencies have requested additional clarity around the requirements for redirect domains. This change is an attempt to make explicit that redirect domains that are currently only serving port 80 must also serve 443 and generally comply with M-15-13.

The change also explains that redirect domains need not (but might want to, especially w/r/t preloading) redirect internally to the https:// version first.

h-m-f-t and others added 2 commits January 16, 2017 16:36
Make explicit the expectations for redirect domains and explain that redirect domains need not (but might want to) redirect internally to the https:// version first.
Comment thread pages/guide.md
### What about domains that are only used to redirect visitors to other websites?

These domains must enable port 443, use and enforce HTTPS, and follow all the same requirements and guidelines as domains used to host websites and APIs, including HSTS and preloading.
These domains must enable port 443 and use properly configured HTTPS.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What "enforce HTTPS" means for redirect domains is ambiguous here, and is what the subsequent answer now addresses, so I changed it to "properly configured".

Comment thread pages/guide.md

For example, it is not required by M-15-13 to redirect from `http://example.gov:80` to `https://example.gov:443` before redirecting to `https://another-example.gov:443`. However, doing so enables the connecting client to see and cache the HSTS header on `example.gov`, which it may not otherwise see.

However, doing an internal redirect first **is required** [to automatically preload second-level domains](https://hstspreload.org/#submission-requirements), and so this practice is recommended for second-level domains.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is technically possible to preload non-second-level-domains (and I've done so before) but it requires manual interaction with the Chrome HSTS preload team. I adjusted it to be a little more precise about that.

Comment thread pages/guide.md
* [Do I need to shut off port 80?](#do-i-need-to-shut-off-port-80%3f)
* [What does "all Federal agency domains or subdomains" include?](#what-does-"all-federal-agency-domains-or-subdomains"-include%3f)
* [What about domains that are only used to redirect visitors to other websites?](#what-about-domains-that-are-only-used-to-redirect-visitors-to-other-websites%3f)
* [Do domains that redirect to other external domains need to redirect internally to HTTPS before redirecting externally?](#do-domains-that-redirect-to-other-external-domains-need-to-redirect-internally-to-https-before-redirecting-externally%3f)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Each FAQ answer also gets a link in the ToC at the top of the page for easy navigation.

@konklone
konklone merged commit a76ad92 into master Jan 16, 2017
@konklone
konklone deleted the redirect-clarity branch January 16, 2017 23:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants