no idea the root cause. but here is my points:
1, I’d use the / with hostname in the map: map https://gateway.mydomain.com/ https://app.mydomain.com/ that may help reducing some bad situation where ATS may … 2, the last redirect to www looks like a forward proxy behavior? 3, always consider the http_ui & debug tags in records.config, for the cache and http transactions. hopes that will help - Yongming Zhao 赵永明 在 2014年4月24日，上午10:28，Frank Smith <[email protected]> 写道： > I am new to the Traffic Server and I could use some help because I have some > odd behavior, which could be my ignorance, or perhaps an issue. > > So, I have an HTTPS server we will call gateway.mydomain.com reverse proxying > to my application serverapp.mydomain.com, which is also HTTPS. > > So, I have my remap.config with: > > map https://gateway.mydomain.com/ https://app.mydomain.com > > (and I have tried both with and without this next line) > > reverse_map https://app.mydomain.com https://gateway.mydomain.com > > When I front this through my browsers, both Chrome and IE, I get an error > about page not found or something (these user friendly messages are hard to > understand what is happening under the hood). > > When I tail the extended2.log file during my reverse proxy request, I see the > GET to https://app.mydomain.com with a 302 status. > > However, I can pull up directly online my origin server - > https://app.mydomain.com through a web browser with no problem, as we are > still testing this configuration - eventually we will move the > app.mydomain.com behind the proxy server. I should note that I work on the > proxy team, and don't have much visibility to the app team - any questions I > should ask of them, would be greatly appreciated. > > To isolate the problem, I logged into the Traffic server, and issued a wget > to the app.mydomain.com and I got the exact same response I get in a web > browser. > > So, then I wget against my gateway server - https://app.mydomain.com, and I > get it trying to redirect to www.mydomain.comand not finding that in the DNS, > it bombs. I have no idea why it is trying to redirect there, and it doesn't > try when I make the request directly with a web browser or wget (on the > server). > > So, clearly there is a problem there, but I don't know where/how to hunt the > problem down... > > Thoughts? > > Thanks, > > Frank > > >
