Fix Broken Links in Documentation #881
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…in documentation. When Elasticsearch changed their FQDN from/www.elasticsearch.org to www.elastic.co, they preserved most of their page's paths but didn't setup granular redirect rules. For example: Going to `http://www.elasticsearch.org/contributor-agreement/` will redirect browsers to https://www.elastic.co/, but drop the path `/contributor-agreement/`.
|
thanks @nodanaonlyzuul ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When Elasticsearch changed their FQDN from
www.elasticsearch.orgtowww.elastic.co,they preserved most of their page's paths but didn't setup granular redirect rules.
For example:
Going to
http://www.elasticsearch.org/contributor-agreement/will redirect browsersto https://www.elastic.co/, but drop the path
/contributor-agreement/.Contributing
I have signed the CLA. I haven't found any open issues that reference this problem.
Thanks to all maintainers for their work on this library - let me know if there's any additional work you'd like to see in this PR.