Right.. I tested Duke's master branch a few month's back and didnt see
the 'random' 60ms ttms that I see in 7.1.4.
On Mon, Mar 15, 2021 at 10:24 AM Alan Carroll
wrote:
>
> I would expect the 60ms ttms is due to the event loop timing - that because
> of the DNS callout, there is a miss which then
re: 60ms ttms
take a look at the below.
https://github.com/apache/trafficserver/pull/6234
https://github.com/duke8253/trafficserver/commit/159ae2510f0e2dab0907bdf2aec1ce74da0b3653
On Wed, Mar 10, 2021 at 9:07 AM Nick Dunkin wrote:
> Hi,
>
>
>
> I wanted to raise an interesting issue we discov
Ok.. on your child server, set your parent.config to use: parent_is_proxy=false
"the list of parents and secondary parents are the origin servers
go_direct flag is ignored and origins are selected using the specified
round_robin algorithm. The FQDN is removed from the http request
line."
Your ch
ensure your parent cache will recognize requests for
originserver.cdn.lab:8080
This below is the request to your parent cache.
GET http://originserver.cdn.lab:8080/player.html HTTP/1.1^M
The HOST header in this request will not be honored.
In this context, you have to account for the FQDN seen
also.. using curl(without the insecure option), can you poll the
origin server directly without receiving a certificate error ?
On Sun, Mar 1, 2020 at 10:59 AM Jeremy Payne wrote:
>
> If ATS to origin cert validation is failing, then you may need to
> disable server verify(that&
If ATS to origin cert validation is failing, then you may need to
disable server verify(that's if your company security policy allows).
Couple different approaches..
https://docs.trafficserver.apache.org/en/latest/admin-guide/files/sni.yaml.en.html#override-verify-origin-server
https://docs.traf
