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.

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

Pick a canonical URL between whatwg.org/specs and spec.whatwg.org #14

Closed
domenic opened this issue Feb 8, 2017 · 4 comments
Closed

Comments

@domenic
Copy link
Member

domenic commented Feb 8, 2017

I prefer the latter.

Then we should 301 one of them into the canonical one.

@foolip
Copy link
Member

foolip commented Feb 9, 2017

I would also prefer spec.whatwg.org.

@annevk
Copy link
Member

annevk commented Feb 12, 2017

For that we need to find a way to redirect /specs and /specs/ but not /specs/somethingelse. (Note that the way this works on the server is that spec.whatwg.org is simply backed by whatwg.org/specs/.

@domenic
Copy link
Member Author

domenic commented Feb 12, 2017

I think that's how .htaccess redirects work in general, right? Maybe you need to surround the path by quotes?

@domenic
Copy link
Member Author

domenic commented Feb 12, 2017

I guess not. However you can use RedirectMatch: http://stackoverflow.com/a/3500556/3191

annevk added a commit that referenced this issue Feb 14, 2017
* Fixes #11 by adding a README.
* Fixes #14 by redirecting /specs/ to spec.whatwg.org.
* Fixes #15 by using spokesperson and removing the mention of HTML5.
* Fixes #13 by redirecting to whatwg/meta for queries.
* Addresses #9 partly by removing one reference to HTML for developers.
* Fixes #3 by mentioning this repository as the source of (potential)
trouble.
annevk added a commit that referenced this issue Feb 14, 2017
* Fixes #11 by adding a README.
* Fixes #14 by redirecting /specs/ to spec.whatwg.org.
* Fixes #15 by using spokesperson and removing the mention of HTML5.
* Fixes #13 by redirecting to whatwg/meta for queries.
* Addresses #9 partly by removing one reference to HTML for developers.
* Fixes #3 by mentioning this repository as the source of (potential)
trouble.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants