On 10/17/2024 08:39 AM, Dan Purgert wrote:
On Oct 17, 2024, Richard Owlett wrote:While trying to follow a discussion involving a deeply nested debian.org sub-directory, I attempted to find the purpose of that sub-directory by following a chain of links titled "Parent Directory". That led to http://ftp.us.debian.org/debian/ whose first link is to "http://ftp.us.debian.org/debian/README"; [NOTE BENE quotation marks]. [...]
Though I understand why Dan clipped [...], it was there for a reason.I date back to CPUs with 12AX7s and spent three decades in component level (engineering support)/(QA/QC)/(end user support).
I pointed my browser to "http://archive.debian.org/debian-archive"; and got: I went back to the link triggering the "404 error" and added a trailing "/" to the URL. It *then* displayed properly. Is this a typo or a server problem? [ understand "STRANGENESS" in my Subject: line? ;]Both, potentially.
'Twas afraid of that ;{
The server SHOULD give you the directory with or without the trailing slash, but it seems it's configured such that if you don't have the trailing slash on the directory, it treats it as a file (which isn't there). 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.