https://bz.apache.org/bugzilla/show_bug.cgi?id=70027
Philippe Cloutier <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED --- Comment #6 from Philippe Cloutier <[email protected]> --- Thanks again Rich That fixes, but I still find the sentence unclear. For me, /var/www/pathwithatypo.jpig is not an *invalid* path just because /var/www/pathwithatypo.jpig does not exist. Indeed, RFC 9110 does not use the term "invalid" with regards to 404 Not Found. Where it does use it is to describe 400 Bad Request (15.5.1.). For example, on Windows, “C:\foo:bar.txt” is an invalid path; no file with such a path can be created. I would recommend to clarify the phrasing or to provide an example. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
