I just got surprised by the existence of proxy.config.http.post_connect_attempts_timeout again while tracking down an issue for the ops team. There is also a proxy.config.http.connect_attempts_timeout which covers the connect timeouts for all the methods expect POST. If you forget to set the post one, you get the default connect timeout of 1800 seconds for POST methods.
https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html?#proxy-config-http-connect-attempts-timeout I presume it was useful to have two distinct timeouts when the connect timeout was really the timeout for time-to-first-byte. Now that the *connect_attempts_timeout just covers the time to complete the TCP or TLS handshake, there is not much point in having a separate control for the POST method.
