Traffic Server : Unable to access Delivery Service (with HTTPS enabled origin URL) when using a MID cache server

[stackexpress-jawed]

I'm submitting a ...

• bug report

Traffic Control components affected ...

• Traffic Server

Current behavior:

I am using a MID cache server above an EDGE cache server and created two Delivery Service.

1. Delivery Service URL - https://cdn.test01.router.<mydomain>.tld , Origin URL - http://example.org (not HTTPS)
2. Delivery Service URL - https://cdn.test02.router.<mydomain>.tld , Origin URL - https://example.com (HTTPS)

Now, I am able to access first Delivery Service URL - https://cdn.test01.router.<mydomain>.tld but when I try to access second Delivery Service URL - https://cdn.test02.router.<mydomain>.tld it's returning following error.

[Jul  8 07:52:34.397] [ET_NET 11] NOTE: Failure threshold met failcount:10 >= threshold:10, http parent proxy mid-01.<mydomain>.com:443 marked down

Edge Cache Server configs -

remap.config

map	https://cdn.test01.router.<mydomain>.tld     http://example.org/ 

map	https://cdn.test02.router.<mydomain>.tld     https://example.com/ 

parent.config

dest_domain=example.org port=80  scheme=http parent="mid-01.<mydomain>.com:80|1.2" round_robin=consistent_hash go_direct=false qstring=consider

dest_domain=example.com port=443  scheme=https parent="mid-01.<mydomain>.com:443|1.2" round_robin=consistent_hash go_direct=false qstring=consider

---

Mid Cache Server configs

remap.config

map http://example.org http://example.org 

map https://example.com https://example.com 

parent.config

dest_domain=example.org port=80  scheme=http parent="example.org:80" round_robin=consistent_hash go_direct=true qstring=ignore parent_is_proxy=false

dest_domain=example.com port=443  schem=https parent="example.com:443" round_robin=consistent_hash go_direct=true qstring=ignore parent_is_proxy=false

Expected behavior:

Able to access second Delivery service.

Minimal reproduction of the problem with instructions:

• Use a MID cache server above the EDGE cache server.
• Create a Delivery service with HTTPS enabled origin URL.
• And try to access the Delivery Service.