Closed
Bug 586001
Opened 14 years ago
Closed 14 years ago
Add rewrite rule to fix broken links on devmo
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sheppy, Assigned: oremj)
Details
We recently reorganized the JavaScript Reference on devmo. Unfortunately, for some reason, Deki failed to generate the redirects on-site that it normally does when pages are moved around. So we now have gazillions of broken links.
Can someone please set up a rewrite rule on devmo to direct:
https://developer.mozilla.org/En/Core_JavaScript_1.5_Reference/ (and all subpages thereof)
to:
https://developer.mozilla.org/en/JavaScript/Reference/ (otherwise the same)
Comment 1•14 years ago
|
||
RewriteRule ^En/Core_JavaScript_1\.5_Reference/(.*) en/JavaScript/Reference/$1 [R,L]
tested with Apache 2.2.15.
Updated•14 years ago
|
Assignee: server-ops → jeremy.orem+bugs
Assignee | ||
Comment 2•14 years ago
|
||
Added.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 3•14 years ago
|
||
This doesn't seem to be working. For example:
https://developer.mozilla.org/En/Core_JavaScript_1.5_Reference/Objects/Array/Sort
This doesn't redirect to:
https://developer.mozilla.org/en/JavaScript/Reference/Objects/Array/Sort
Like it ought to.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 4•14 years ago
|
||
Never mind, the first link was bogus. Dunno where it came from. :)
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Comment 5•14 years ago
|
||
it came from this 2 steps:
1) Google for "javascript sort" , click 3rd entry
2) Go to MDN and search for sort, click 1st entry
Both go to:
https://developer.mozilla.org/En/Core_JavaScript_1.5_Reference/Objects/Array/Sort
which doesn't exist.
This definitely should work, every developer that, like me, google for the javascript functions to get to MDN will get nowhere
I'm reopening the bug - please close it again if I'm talking crap, but I'm just being cautious here
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 6•14 years ago
|
||
I don't know where that link has coming from. That page moved from that location like a year ago; Google shouldn't be pulling that result up anymore.
However, since it is, can we add a rewrite rule like:
RewriteRule ^En/Core_JavaScript_1\.5_Reference/Objects/(.*) en/JavaScript/Reference/Objects/$1
[R,L]
That should fix these links so they work the way people expect, since Google is apparently taking forever to catch up.
Comment 7•14 years ago
|
||
And just out of curiosity, why is MDN's search also pointing to that same link?
Reporter | ||
Comment 8•14 years ago
|
||
The new MDN pages are using Google to do the search. Once you're in the docs, you're using the wiki software's search engine, and you'll get correct links.
Comment 9•14 years ago
|
||
Understood, thanks
Comment 10•14 years ago
|
||
Removing the old links to MDN could be easily done with Google Webmastertools. You can add URLs you want to removed by wildcard and they usually do so within 24 hours.
currently requesting https://developer.mozilla.org/En/Core_JavaScript_1.5_Reference/Objects/Array/Sort results in four redirects:
1.
302 Found
Location http://developer.mozilla.org/en/JavaScript/Reference/Objects/Array/Sort
2.
301 Moved Permanently
Location https://developer.mozilla.org/en/JavaScript/Reference/Objects/Array/Sort
3.
302 Found
Location https://developer.mozilla.org/
4.
301 MOVED PERMANENTLY
Location https://developer.mozilla.org/en-US/
Comment 11•14 years ago
|
||
seeing a lot of complaints about this, so bumping to major. can we figure out what's up with the redirects and also get the google search stuff resolved?
Severity: normal → major
Assignee | ||
Comment 12•14 years ago
|
||
(In reply to comment #10)
> Removing the old links to MDN could be easily done with Google Webmastertools.
> You can add URLs you want to removed by wildcard and they usually do so within
> 24 hours.
>
> currently requesting
> https://developer.mozilla.org/En/Core_JavaScript_1.5_Reference/Objects/Array/Sort
> results in four redirects:
> 1.
> 302 Found
> Location
> http://developer.mozilla.org/en/JavaScript/Reference/Objects/Array/Sort
>
> 2.
> 301 Moved Permanently
> Location
> https://developer.mozilla.org/en/JavaScript/Reference/Objects/Array/Sort
>
> 3.
> 302 Found
> Location https://developer.mozilla.org/
>
> 4.
> 301 MOVED PERMANENTLY
> Location https://developer.mozilla.org/en-US/
In this case comment 6 probably won't fix anything.
Eric, what do you want me to do with this bug?
Comment 13•14 years ago
|
||
Could this extra rewrite rule an option?
RewriteRule ^En/Core_JavaScript_1\.5_Reference/Objects/(.*) en/JavaScript/Reference/Global_Objects/$1 [R,L]
This would fix the urls found by Google, and still would make the content accessible as long the urls are in Google's index.
Assignee | ||
Comment 14•14 years ago
|
||
Eric, is comment 13 what you want to do?
Reporter | ||
Comment 15•14 years ago
|
||
That looks right to me.
Assignee | ||
Comment 16•14 years ago
|
||
Done.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•