Closed Bug 258433 Opened 21 years ago Closed 21 years ago

Remove the document from the server and make the redirect server-side

Categories

(www.mozilla.org :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: annevk, Assigned: nb)

References

Details

fantasai, you can do this, right?
server-side redirect is now in place. You can do what you want with the file in cvs :)
BTW, I think it's more maintainable to put redirects in .htaccess files, which we can do, rather than in the server config.
So there are redirects set up in .htaccess[1] and on the server. I believe the fastest way would be in httpd.conf. If the server admins have access to that file we could probably move all things that are currently spreaded in .htaccess file to that single file and disable .htaccess to improve performance. If .htaccess is enabled Apache will look for every request in every directory if there is a .htaccess file available. For a file that is nested some directories deep this will cause "a lot of looking up". However, I don't know how many access there is and how many flexibility is needed. If we keep .htaccess it would probably be better and more clear if all redirects are put in the root .htaccess file instead of in multiple files. [1]<http://doctor.mozilla.org/?file=mozilla-org/html/.htaccess>
Since we don't want that many bugs. Dave, could you redirect <http://www.mozilla.org/docs/refList/refNSPR/> to <http://www.mozilla.org/projects/nspr/reference/html/>. Thanks. (fantasai or someone else should probably remove the old file afterwards.)
Checking in mozilla-org/html/.htaccess; /cvsroot/mozilla-org/html/.htaccess,v <-- .htaccess new revision: 1.10; previous revision: 1.9 done I'll have to wait until I get home to remove the old file. Doctor doesnt support deletions AFAIK.
Finished. Redirect added, old file cvs removed.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Lets leave this one open for other possible redirects and general discussion about .htaccess/httpd.conf (and server, if that is different from httpd.conf). (Besides, did you remove the original file this bug was opened for as well?)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
The bug-form.html redirect has been created and old file removed. I will leave this bug open per your request
I prefer .htaccess files for Redirects since they're much easier to administer. (Anyone with CVS access can change them.)
Oh, and I also prefer using nested .htaccess files over the root .htaccess since there's much less for the server to do -- the load on our server is mostly getting a very small number of pages (home page and start pages and the css and images that they use), so if the page in question isn't in one of those directories, I'd think the redirect is better off out of the critical path. Then again, I don't really know how apache implements this stuff, but I doubt having a products/firebird/.htaccess file hurts performance when somebody loads the home page.
You are correct in that. However, if someone loads /products/firefox/, /.htaccess, /products/.htaccess and /products/firefox/.htaccess will be checked. Having everything specified in httpd.conf makes that zero check ups. The difference is probably not noticeable though, since Apache is very fast :-). If we choose this route, all the non-root redirects should be moved to the deepest folder possible. For example (no line breaks, using them for showing it here): # Redirect permanent /releases/stable.html # http://www.mozilla.org/products/mozilla1.x/ ... should be moved to the 'releases' directory.
<http://doctor.mozilla.org/doctor.cgi?action=edit&file=http://www.mozilla.org/catalog/end-user/.htaccess> The following should come in that file: # Redirect gone /release (That file was linked from bug 151557, but it has been removed and not been redirected, which basically means it is gone. However, it returns a 404...)
Status: REOPENED → ASSIGNED
RCS file: /cvsroot/mozilla-org/html/catalog/end-user/.htaccess,v done Checking in .htaccess; /cvsroot/mozilla-org/html/catalog/end-user/.htaccess,v <-- .htaccess initial revision: 1.1 done
Taking.
Assignee: fantasai.bugs → nbebout
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
We need to have .htaccess to be able to do per-directory or per-file charset overrides, too, if we implement a server-wide UTF-8 charset (which a lot of people, including myself, really really want ;) )
The following page should be a 301, not a page: <http://www.mozilla.org/bugs/changes.html> It should redirect permanently to: <http://www.bugzilla.org/status/changes.html>
Summary: Remove the document from the server and make the redirect server-side (bug-form.html) → Remove the document from the server and make the redirect server-side
This page: <http://www.mozilla.org/bugs/report.html> Should redirect to: <http://www.mozilla.org/quality/bug-writing-guidelines.html> The latter is much more clear and includes all the information /bugs/report.html has.
This page: <http://www.mozilla.org/glimpsesearch.html> Should redirect to: <http://www.mozilla.org/> Just like 'search.html' does. This page: <http://www.mozilla.org/feedback.html> Should redirect to: <http://www.mozilla.org/contact/> If people think that should not happen, one of the two documents should be rewritten and they should point to each other. It should also be clear what the document purpose is in that case.
This document: <http://www.mozilla.org/download-mozilla.html> Should redirect to: <http://www.mozilla.org/source.html> It should not redirect to /download.html since it is about source code.
This document: <http://www.mozilla.org/index2.html> Should redirect to: <http://www.mozilla.org/>
Depends on: 258047
fantasai, is it ok for me to implement these redirects?
I would hold off on - the download-mozilla.html one (we need to organize Mozilla's download/cvs/build info first) - the feedback.html one (I need to contact website-drivers on this one.) wrt download pages: - /download/ can redirect to download.html, sure, but - /products/mozilla1.x/download/ should redirect to /products/mozilla1.x/ Other than that, the rest seem ok to me.
Here's another one to add to the list: bug 260109
Alias: redirect
Depends on: 260109
download-mozilla.html shoould not redirect to source.html because source.html links to it for ftp tarball download information.
Oops, fantasai already commented about download-mozilla.html. sorry for the extra spam. These should all be fixed except for the ones mentioned in comment 26
Status: ASSIGNED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
How was this fixed? I get 404s when I go to the pages that should give 301s.
I need to look into this.... Something is making some of the redirects not work. BTW, I didn't mean to resolve this. I had the wrong tab active when i clicked resolve as fixed. I meant to resolve the book of mozilla bug.
Status: REOPENED → ASSIGNED
These should all be fixed now.
I still get the same problem as before. Are the redirects set up correctly?
These all WFM. Which ones do not work for you?
Heh, > Comment #32 From Nicholas Bebout 2004-11-13 16:18 > Comment #33 From Anne van Kesteren 2004-11-13 16:32 They work fine. Thanks for fixing them. -> RESOLVED FIXED.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → FIXED
Alias: redirect
Product: mozilla.org → Websites
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.