----- Original Message -----
> Hi there,
>
> I've got some way along to setting up a couple of ats instances as
> child and parent.  As it stands, if I send my GET to the parent, or
> stop ats on the parent and send to the child, either way I get back
> the desired object (the child failing back to going direct).
>  However,
> if I send the request to the child while the parent is available,
> what
> I get returned is a little garbled, as follows - names changed to
> protect the guilty.

I'm a little confused. But fortunately, whenever I am, I remember
to ask the simple questions, like:
 What, exactly, does the error log say.

Or, as it may be the case here:

   Are you using ATS as Forward or Reverse proxy?

> My GET to the child reads:
> GET / HTTP/1.0
> Host: www.site.com
>
> Netcat on the parent cache port hears:
> GET http://origin.site.com/ HTTP/1.1
> Host: www.site.com
> Client-ip: 127.0.0.1
> X-Forwarded-For: 127.0.0.1
> Via: http/1.0 debian6vm1[7F000001]
> (ApacheTrafficServer/3.1.1-unstable
> [uScMs f p eN:t cCMi p s ])
>
> I have just one rule in remap.conf:
> regex_map       http://((cdn)?www\.)?.site.com/
>       http://origin.site.com/
>
> Just writing this out I've had the brainwave that perhaps edge caches
> shouldn't be doing the mapping at all - but I'm reluctant to disable
> remap_required.... but anyway it's clear to me that having
> origin.site.com in the GET is a bit weird.  Any help on where to go
> from here would be much appreciated!
>
> Best
> Tom


i

--
Igor Galić

Tel: +43 (0) 664 886 22 883
Mail: [email protected]
URL: http://brainsware.org/
GPG: 6880 4155 74BD FD7C B515  2EA5 4B1D 9E08 A097 C9AE

Reply via email to