Chenjp commented on PR #771: URL: https://github.com/apache/tomcat/pull/771#issuecomment-2441143076
> +1 for the third one (the request will not work so it's better to send the specified 400 code immediately), I just fixed it. For the other two, about depth, I left it as is on purpose. There's no status code mentioned for a bad depth, and there's a default value if absent. IMO pretending it's either 0 if specified or inifinity otherwise is not bad. Note: There are some items where you must not be strict like the lock timeout just after the depth header in the code. Per rfc4918 [10.2](https://datatracker.ietf.org/doc/html/rfc4918#section-10.2). Depth Header defines: Depth = "Depth" ":" ("0" | "1" | "infinity") Others may be considered as ```400 Bad Request```. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
