bryancall commented on issue #9176: URL: https://github.com/apache/trafficserver/issues/9176#issuecomment-4828016736
This is a configuration and usage question rather than a defect in Apache Traffic Server, so I am closing it as a stale support request. As noted earlier in the thread, the certifier plugin only generates server certificates when the Transport Layer Security (TLS) handshake terminates on the proxy, which is the transparent proxy path (marking and TPROXY-ing traffic into Traffic Server via iptables), not an explicit forward proxy that forwards the CONNECT method to an origin. The self-routing problem you described (the localhost loop being blocked by SELF_DETECT being marked down) is a parent selection and host status configuration matter, not a code bug. The transparent proxy configuration is documented at https://docs.trafficserver.apache.org/admin-guide/configuration/transparent-proxy.en.html and the certifier plugin at https://docs.trafficserver.apache.org/admin-guide/plugins/certifier.en.html . For further help with this kind of deployment question, the [email protected] che.org mailing list is a better venue than the issue tracker. If you do find a concrete, reproducible bug in the certifier plugin or in self-routing, please open a new issue with the exact configuration and steps to reproduce, and we can take another 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]
