I think this is because we are already in the process of redirecting, and so disabling redirect for the transaction here would be too late.
This is tricky because of the way the state machine transitions are set up. What we need to do is resolve the target (`Location`) of the redirect response and then check the resulting address against our configuration in order to figure out what the administrator wants to do. But we only proceed to the DNS lookup state *after* we have "committed" to following the redirect. * If we disable redirect for the transaction too early, we will not be able to resolve the host and we will potentially return responses we should have followed or rejected. * If we wait until after host resolution to disable redirect for the transaction, then the logic will have no effect, and we will potentially follow redirects that we should have returned or rejected. [ Full content available at: https://github.com/apache/trafficserver/pull/4145 ] This message was relayed via gitbox.apache.org for [email protected]
