Ah -- the redirect remap rule-- had forgotten that existed! So that doesn't need or talk to any other machine. I'm a bit confused about what the 2 curls are -- one has Server: ats 5, and the other Server ATS 9.
Just threw a redirect on one of ours: remap.config: redirect http://example.com/ http://httpbin.org/dripi.aspx?numbytes=10000&duration=1&delay=1&code=200 [18:49:02]$ curl -sIXGET --resolve example.com:80:127.0.0.1 " http://example.com"; | grep -i Location Location: http://httpbin.org/dripi.aspx?numbytes=10000&duration=1&delay=1&code=200 [18:49:13]$ curl -sIXGET --resolve example.com:80:127.0.0.1 " http://example.com/foo/bar"; | grep -i Location Location: http://httpbin.org/dripi.aspx?numbytes=10000&duration=1&delay=1&code=200/foo/bar [18:49:22]$ curl -sIXGET --resolve example.com:80:127.0.0.1 " http://example.com/foo/bar.aspx?foo=bar"; | grep -i Location Location: http://httpbin.org/dripi.aspx?numbytes=10000&duration=1&delay=1&code=200/foo/bar.aspx?foo=bar Is the second machine (the white background screeny) proxying to the first (black background)? miles On Sat, Mar 27, 2021 at 2:21 PM Patrick Andrews <[email protected]> wrote: > Everything on the server is mostly default. It just seems as, from what I > can gather, the redirect reply isn't sending the fully configured url > despite having that configuration as instructed. I'm not quite sure where > else to look or tweak. > > Let me know if the details I sent weren't sufficient. > > On Sat, Mar 27, 2021 at 5:00 PM Patrick Andrews <[email protected]> > wrote: > >> Hey Miles, >> >> Curl from the server: >> [image: image.png] >> >> and the response I'm getting on my service box is as follows: >> >> [image: image.png] >> >> >> You'll notice that the redirect gets cut off via the .aspx. I am aware of >> the Dynamic Content Caching configuration required in records.config and do >> have it on: >> >> CONFIG proxy.config.httpcache.cache_urls_that_look_dynamic INT 1 >> >> >> On Sat, Mar 27, 2021 at 4:52 PM Patrick Andrews <[email protected]> >> wrote: >> >>> Standby I did not finish my reply. That is simply the remap rule. >>> Apologies. >>> >>> On Sat, Mar 27, 2021 at 4:51 PM Patrick Andrews <[email protected]> >>> wrote: >>> >>>> Hey Miles, >>>> >>>> Thrilled I got a response so quickly. If you can imagine a >>>> beleaguered sysadmin who's been trying to get this to work for too many >>>> hours now then you've got a good image where I'm at. Here's what I've got: >>>> >>>> a) remap rule is as follows: >>>> [image: image.png] >>>> >>>> >>>> On Sat, Mar 27, 2021 at 4:47 PM Miles Libbey <[email protected]> >>>> wrote: >>>> >>>>> When you say "redirecting" do you mean returning a 301/302/303/307/308 >>>>> status code? >>>>> >>>>> Can you share >>>>> a) the remap rule >>>>> b) a curl with response headers through your ATS instance -- like curl >>>>> -s -IXGET --resolve www.example.com:443:127.0.0.1 >>>>> "https://www.example.com/"; >>>>> c) a curl with response headers to the origin used (like ATS would >>>>> send to it >>>>> and d) what headers/response you were expecting? >>>>> >>>>> thanks! >>>>> miles >>>>> >>>>> On Sat, Mar 27, 2021 at 1:27 PM Patrick Andrews < >>>>> [email protected]> wrote: >>>>> > >>>>> > I'm having some issues with getting ATS to redirect to a link >>>>> containing .aspx. I am aware of the config setting in records.config and >>>>> dynamic caching and have made the configuration changes as per the >>>>> documentation. When I analyze the redirect via wireshark, however, I am >>>>> still seeing that it's not redirecting properly the entire URL. I have an >>>>> older box running version 6 so I know that at one point it was capable of >>>>> doing so. Is there somewhere else I'm missing or have to configure? >>>>> > >>>>> > Thanks. >>>>> >>>>
