bryancall commented on issue #5900: URL: https://github.com/apache/trafficserver/issues/5900#issuecomment-4827338042
I am closing this as a stale configuration question. It was filed in 2019 against Apache Traffic Server 7.1.x and 8.0.3, both of which are end-of-life, and it has had no further detail or activity since. The behavior you saw is by design: when a URL "looks dynamic" (for example, it contains a question mark) and proxy.config.http.cache.cache_urls_that_look_dynamic is off, Traffic Server skips the cache lookup and tunnels the request, which changes how the transaction is handled. Enabling that setting (or setting a Time To Live on the object) keeps the request on the normal cacheable path. The round-robin retry logic controlled by proxy.config.http.connect_attempts_rr_retries is still present on current master and is independent of this setting. If you can still reproduce a case on a currently supported release where connect_attempts_rr_retries does not retry another origin on a connect failure, please open a new issue with the records configuration and a reproduction, and we will t ake a fresh look. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
