Hi, On Thu, Oct 17, 2024 at 09:10:35AM -0500, Richard Owlett wrote: > On 10/17/2024 08:39 AM, Dan Purgert wrote: > > I wonder if apache is doing some kind of directory-level > > virtualization, where it only "exists" if you have the trailing > > slash on the end (I don't know enough of the internals of apache2 to > > say one way or the other; but I have run into this with certain > > configurations of various FTP / SFTP implementations in "commercial" > > products for business communication). > > The *clipped* portion of my post included at least one URL with no > trailing "/" which worked properly.
Two different URLs on the same host can be configured to work completely differently, and also URLs don't have to bear any resemblance to the filesystem underneath (or any filesystem at all). So for example just because requesting http://example.com/foo/ does one thing implies nothing about what requesting http://example.com/bar will do. Either, both or neither of them may relate to actual files and directories on a filesystem somewhere, or perhaps they are generated dynamically from some database. There is no way to tell without being familiar with the backend. In general it is not desirable for the presence or lack of a trailing '/' on something that's meant to be a representation of a container (like a directory/folder) to act differently, so I'd say this case is a minor misconfiguration. That is, in general, if http://example.com/foo/ is expected to show some things that are logically "inside" /foo, then it is considered poor user experience for http://example.com/foo to not do the same. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
