[
https://issues.apache.org/jira/browse/TS-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215550#comment-15215550
]
Muhammad Faisal commented on TS-4294:
-------------------------------------
The issue is not actually related to ATS of any version 5.x or 6.x. The problem
was with the routing of packets. The reverse path for tcp port 80 traffic was
incorrect therefore the client was unable to communicate with the destination.
It is worth mentioning with full transparency setup of ATS it is vital to
review the policy routing (for HTTP traffic) of all ingress and egress traffic
to avoid routing loops.
We can close this issue.
> Error 502 on specific destinations after redirecting http streams to ATS
> ------------------------------------------------------------------------
>
> Key: TS-4294
> URL: https://issues.apache.org/jira/browse/TS-4294
> Project: Traffic Server
> Issue Type: Bug
> Affects Versions: 6.1.1
> Environment: Cent OS 6.7
> Reporter: Muhammad Faisal
> Fix For: 6.2.0
>
>
> ATS version: 6.1.1
> Service Impacting Issue
> We came across an issue when placed ATS in the production environment. We
> have setup ATS with TPROXY as transparent caching for http traffic. The ATS
> box is connected on a single NIC to upstream router. The policy based routing
> is used to redirect traffic towards ATS box.
> We redirected some 4000 clients to ATS box, the clients were having
> established http connections when redirected to ATS. After shifting traffic
> in the error.logs we observed several 502 errors for some origins.
> The following tried but failed:
> Disabling/Re-enabling:
> proxy.config.http.keep_alive_enabled_out
> proxy.config.http.keep_alive_post_out
> Cold reboot
> Thanks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
