Child node not fetching from Parent node

[Patrick O'Brien <pa...@tetrisblocks.net>]

Hello,

When doing a remap on a child node from http => https, I am unable to
have the child nodes pull cached objects from the parent nodes. If I
remove the remap from the child nodes it works, however that means
that if all parents are down we wouldn't be able to fetch the object
properly.

I was under the impression that if we set `CONFIG
proxy.config.url_remap.remap_required` to 0, this would have the child
nodes first check the parent cache. It appears that regardless of what
that value is set to the child never checks the parent if the remap is
http => https. I did notice that http => http remaps fetched from the
parent properly, so I think this is just limited to http => https.

I am using Apache Traffic Server version 6.2.x on CentOS 7.x. Here are
my configs:

records.config (parent):
https://gist.github.com/poblahblahblah/728e51d614b4b349542a1ca70d7c7782
records.config (children): same as parent

remap.config (parent):
https://gist.github.com/poblahblahblah/a0278f9d1b99cad326265b1c68aaab34
remap.config (children):
https://gist.github.com/poblahblahblah/86cb171fe859c2d610b0e7e2c08dab8d

parent.config (parent): blank file
parent.config (children):
https://gist.github.com/poblahblahblah/6e760aa13384882be59ac85b2bdbbdae

cache.config: (parent):
https://gist.github.com/poblahblahblah/83634a586b337121e9bc9c0a015622fb
cache.config: (children): same as parent

I also tried to add the suggested remap of `http://s3.amazonaws.com
http://s3.amazonaws.com` to the parent's remap config, but that didn't
work. I also tcpdumped the parent while testing and didn't see the
children making any connection attempts to the parent when the http =>
https remap was in remap.config. Going further, I set `go_direct` to
false on the children and this caused the request to fail.

I thought that this might be a 6.2.x issue so I built against
662be1f88be80e701634ece6ab82c16094250bf6 from git to test out 7.x.
Using any remap with trafficserver against this binary caused a crash.

child HEAD crash stdout/stderr:
https://gist.github.com/poblahblahblah/e3b4f50c6b99499811d703cdafbf53b2
child HEAD crash log:
https://gist.github.com/poblahblahblah/8455facfe32fb565d710019f65946039

-patrick

Re: Child node not fetching from Parent node

[John Rushford <jj...@gmail.com>]

Patrick,

In the parent.config on the children there is no match found for https 
so thats why you see no connect to the parents.  I believe you would 
need entries like these on the children in parent.config:

dest_domain=s3.amazonaws.com scheme=https parent="proxy1:443" 
round_robin=true

dest_domain=. parent="proxy1:8080" round_robin=true

The parents I believe, would also need to terminate the ssl connection 
by listening on port 443 and have the proper certificates

John

On 12/19/16 12:01 PM, Patrick O'Brien wrote:
> Hello,
>
> When doing a remap on a child node from http => https, I am unable to
> have the child nodes pull cached objects from the parent nodes. If I
> remove the remap from the child nodes it works, however that means
> that if all parents are down we wouldn't be able to fetch the object
> properly.
>
> I was under the impression that if we set `CONFIG
> proxy.config.url_remap.remap_required` to 0, this would have the child
> nodes first check the parent cache. It appears that regardless of what
> that value is set to the child never checks the parent if the remap is
> http => https. I did notice that http => http remaps fetched from the
> parent properly, so I think this is just limited to http => https.
>
> I am using Apache Traffic Server version 6.2.x on CentOS 7.x. Here are
> my configs:
>
> records.config (parent):
> https://gist.github.com/poblahblahblah/728e51d614b4b349542a1ca70d7c7782
> records.config (children): same as parent
>
> remap.config (parent):
> https://gist.github.com/poblahblahblah/a0278f9d1b99cad326265b1c68aaab34
> remap.config (children):
> https://gist.github.com/poblahblahblah/86cb171fe859c2d610b0e7e2c08dab8d
>
> parent.config (parent): blank file
> parent.config (children):
> https://gist.github.com/poblahblahblah/6e760aa13384882be59ac85b2bdbbdae
>
> cache.config: (parent):
> https://gist.github.com/poblahblahblah/83634a586b337121e9bc9c0a015622fb
> cache.config: (children): same as parent
>
> I also tried to add the suggested remap of `http://s3.amazonaws.com
> http://s3.amazonaws.com` to the parent's remap config, but that didn't
> work. I also tcpdumped the parent while testing and didn't see the
> children making any connection attempts to the parent when the http =>
> https remap was in remap.config. Going further, I set `go_direct` to
> false on the children and this caused the request to fail.
>
> I thought that this might be a 6.2.x issue so I built against
> 662be1f88be80e701634ece6ab82c16094250bf6 from git to test out 7.x.
> Using any remap with trafficserver against this binary caused a crash.
>
> child HEAD crash stdout/stderr:
> https://gist.github.com/poblahblahblah/e3b4f50c6b99499811d703cdafbf53b2
> child HEAD crash log:
> https://gist.github.com/poblahblahblah/8455facfe32fb565d710019f65946039
>
> -patrick