Since there are quite some pages linking to the pages on texturizer.net, permanent redirects should be set up. <http://www.google.com/search?q=link:http://texturizer.net/mozilla/jp/firefox/> <http://www.google.com/search?q=link:http://texturizer.net/firefox/index.html> And there are probably more examples. I also think, although it makes it a bit more complicated that for example <http://texturizer.net/firefox/keyboard.html> should redirect to <http://www.mozilla.org/support/firefox/keyboard> (without the extension) and <texturizer.net/firefox/bla> probably shouldn't redirect at all. This can't be fixed until bug 260737 is fixed, but some work for the Firefox pages can certainly be done.
I will fix bug 260737, then this one.
Status: NEW → ASSIGNED
Priority: -- → P2
As I recall using a 403 is the right way (since search engines know the link is dead when indexing, and know where the new URL is). For an apache htaccess file: Redirect Permanent /old/file.shtml http://new.url/foo/bar
403 is Forbidden, actually. The syntax you gave is correct, though. (301, permanent redirect.)
Yes, correct. (was working with it not to long ago too).
Kohei, you should not point to the index file of a directory directly. Link to /.
Created attachment 172869 [details] Firefox/Thunderbird Help (ja-JP) redirects v2 > Kohei, you should not point to the index file of a directory directly. Link to /. Oh, ok.
Attachment #172864 - Attachment is obsolete: true
Created attachment 172994 [details] .htaccess This is what I use
Attachment #172869 - Attachment is obsolete: true
Status: ASSIGNED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
Looks good! Thanks.
Status: RESOLVED → VERIFIED
Created attachment 173051 [details] .htaccess I forgot to redirect ja-JP themes/extensions section to Mozilla Update. Please update your .htaccess. I removed "os=Windows". Thanks.
Thanks, I've updated the file. Please file a new bug if you find more problems, as this bug is marked as verified.
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.