3 ms·
HTTP/1.1 Status Code Definitions : https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html It has alwa
by Cullinet 5y ago
HTTP/1.1 Status Code Definitions :
https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
It has always bugged me, e.g. to get 403: Forbidden when the intended message and situation is 401: Unauthorised.
I am mesmerised to this day why HTTP, maybe a rapidly enforced required HTTP/1.2 spec, didn't make it mandatory for servers to enforce strict management of URI errors especially, together with a crud layer of enforcement and even FTP protocol extensions for providing a UI to enable intelligent use as standard. For example :
if you follow the standard date formats including the date in the filename, it's trivial to implement
300: Multiple Choices
whenever you confirm that you really do want to upload
_National_News_Headlines_for_1995.12.25.htm
after _National_News_Headlines_for_1995.12.24.htm