You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2014-02-15.20:35:23.605>created_at=<Date2014-02-12.14:55:47.628>labels= ['docs']
title='Documentation with two slashes in URL links to v2.6.5c2'updated_at=<Date2014-02-15.20:35:23.584>user='https://bugs.python.org/DanielEllis'
After glancing at the upper-left hand corner, I wondered why Google was sending people to the 2.6 documentation, and a release candidate at that. After checking out the URL, it became obvious that there's an issue somewhere in the Python docs that is causing this.
Quite a bizarre and obscure bug, but probably should be fixed since a major search engine is passing front-page search traffic there.
Presumably there's a RewriteRule that fails to match with the doubled-slashes, so Apache falls through to the filesystem. Maybe there's an old 'current' symlink that's pointing at 2.6.5c2.
I zapped the 2.6.c2 docs. I don't particularly feel like messing with mod_rewrite horrors on python.org to fix it to redirect properly. I think we should drop redirects those soon anyway. Probably will happen with the new site...
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: