 | | Re: Stick in the mud...
|
| (...) Do you mean that if a browser requested some page /foo/bar which didn't exist, but a page /foo/bar/ existed, that it would be nice if the server output the content of /foo/bar/ when it was requested to serve /foo/bar ? If so, wouldn't that (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
| | |  | | Re: Stick in the mud...
|
| (...) What filesystem allows file bar and directory bar in the foo directory? The only way to utilize the above hypothetical URL's is to use mod-rewrite (or similar). You could easially disable slash-optional rewrite when a mod-rewrite rule is (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
| | |  | | Re: Stick in the mud...
|
| (...) wouldn't (...) /foo/bar/ (...) Optionally yes. The admin could choose the least expensive mode to operate in, redirect or rewrite (probably redirect now that you mention it). KL (26 years ago, 13-Jun-00, to lugnet.admin.general)
| | |  | | Re: Stick in the mud...
|
| (...) Yeah, I've been wondering this too. It's pretty longstanding practice in unix that "ls /usr" and "ls /usr/" are going to get me exactly the same thing. For that matter, "stat /usr" and "stat /usr/" both get me the same thing.... And I'm (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
| | |  | | Re: Stick in the mud...
|
| (...) Ah, that makes sense. Really, in order for the proposed ("/foo/bar" exactly equals "/foo/bar/") scheme to work, there needs to be _no_ default index.html file. Or rather, directory index files need to be special in some way. (Just like you'd (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
| |