To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.admin.generalOpen lugnet.admin.general in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Administrative / General / 6911
6910  |  6912
Subject: 
Re: Stick in the mud...
Newsgroups: 
lugnet.admin.general
Date: 
Tue, 13 Jun 2000 20:37:03 GMT
Viewed: 
1298 times
  
In lugnet.admin.general, Todd Lehman writes:
In the general case, however, URLs != filenames.  You could easily have a
URL-to-file mapping layer which converts /foo/bar to /foo/bar.bork and
/foo/bar/ to /foo/bar/index.bork, in which case your two URLs /foo/bar and
/foo/bar/ could both peacefully coexist in the filesystem, even with a one-to-
one mapping.  Since this is likely to confuse (or confound :-) users, it's
probably a good idea to help a user get to /foo/bar/ if they accidentally
arrive there via /foo/bar and /foo/bar doesn't exist while /foo/bar/ does
exist.


In this example, if /foo/bar doesn't exist the user should get what /foo/bar/
points to, one way or another.  Not a page to help them get to it.
Either redirect (current practice) or rewrite (possible option) /foo/bar
to /foo/bar/.  If you invoke other rewriting rules (required to allow the
ambiguity above) the possible automatic rewriting
could be automatically disabled.  That way only the exceptional case you
described would require an exception condition (in code or configuration)
and the default case (no possible ambiguity between /foo/bar and /foo/bar/)
operates as transparently to the user and admin as possible.

KL



Message has 1 Reply:
  Re: Stick in the mud...
 
(...) I agree that this is ideal in cases where the user may have mis-typed the URL by hand (or had been given the wrong URL from, say, a print ad in a magazine, and they typed it in by hand). I'm not sure it's ideal for cases where someone (...) (24 years ago, 13-Jun-00, to lugnet.admin.general)

Message is in Reply To:
  Re: Stick in the mud...
 
(...) On servers where URLs map directly to filespecs, you can't have both /foo/bar and /foo/bar/ unless the underlying filesystem differentiates between the two. I'm not aware of any filesystems which simultaneously allow both /foo/bar and (...) (24 years ago, 13-Jun-00, to lugnet.admin.general)

85 Messages in This Thread:



























Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR