 | | Re: Stick in the mud... —Kevin Loch
|
| | | (...) I think trailing slashes should be optional by specification. Even if they are not optional in the spec, it is optional in the De Facto spec given the existing base of installed servers that handle it gracefully (to the end user). It would be (...) (24 years ago, 13-Jun-00, to lugnet.admin.general)
|
| | | |
| | | | | Re: Stick in the mud... —Todd Lehman
|
| | | | (...) 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 (...) (24 years ago, 13-Jun-00, to lugnet.admin.general)
|
| | | | |
| | | | | | Re: Stick in the mud... —Kevin Loch
|
| | | | | (...) 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 (24 years ago, 13-Jun-00, to lugnet.admin.general)
|
| | | | | |
| | | | | | Re: Stick in the mud... —Matthew Miller
|
| | | | | (...) 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 (...) (24 years ago, 13-Jun-00, to lugnet.admin.general)
|
| | | | | |
| | | | | | Re: Stick in the mud... —Tim Courtney
|
| | | | (...) Isn't it possible for the server to generate a /foo/bar page when its requested, and see that /foo/bar/ exists, then auto-redirect the user to /foo/bar/, therefore evading this problem? -Tim (24 years ago, 13-Jun-00, to lugnet.admin.general)
|
| | | | |
