4 ms·
The trailing / on the URL causes it to 404 for me.
by yuliyp 3y ago
The trailing / on the URL causes it to 404 for me.
- anigbrowl 3y agoHN adds it automatically if it's not included, I don't know why it sometimes fails.
- jonny_eh 3y agoPoorly configured web servers
- jstanley 3y agoNot necessarily. "/foo/" and "/foo" are different URLs. In my view HN is wrong to add the trailing slash (if indeed it does do that). I guess it is an effort towards deduplication.
- chmod775 3y agoIt would even be less wrong to remove trailing slashes instead, because it's a path segment separator and there's no segment here after the last the slash. It's a rather odd choice to be adding slashes.
- blacksmith_tb 3y agoBetting it was an attempt to change bare domain urls from 'www.example.com' to 'www.example.com/' which is reasonable, but not for something with more path than that.
- jonny_eh 3y agoThey should at least redirect to the correct url.
- timbit42 3y agoNormally a slash indicates a folder on the web site and the server will look for and serve an index.html or index.php file in that folder. Without the slash indicates a filename, even if it doesn't have an extension. That said, there are many sites that rewrite URLs allowing anything to be anything.