From users-return-8370-archive-asf-public=cust-asf.ponee.io@trafficserver.apache.org Mon Jan 11 19:05:16 2021 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mxout1-ec2-va.apache.org (mxout1-ec2-va.apache.org [3.227.148.255]) by mx-eu-01.ponee.io (Postfix) with ESMTPS id A2858180638 for ; Mon, 11 Jan 2021 20:05:16 +0100 (CET) Received: from mail.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by mxout1-ec2-va.apache.org (ASF Mail Server at mxout1-ec2-va.apache.org) with SMTP id D99E643B56 for ; Mon, 11 Jan 2021 19:05:15 +0000 (UTC) Received: (qmail 73185 invoked by uid 500); 11 Jan 2021 19:05:15 -0000 Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@trafficserver.apache.org Delivered-To: mailing list users@trafficserver.apache.org Received: (qmail 73175 invoked by uid 99); 11 Jan 2021 19:05:15 -0000 Received: from spamproc1-he-de.apache.org (HELO spamproc1-he-de.apache.org) (116.203.196.100) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jan 2021 19:05:15 +0000 Received: from localhost (localhost [127.0.0.1]) by spamproc1-he-de.apache.org (ASF Mail Server at spamproc1-he-de.apache.org) with ESMTP id 6FE0D1FF3A4 for ; Mon, 11 Jan 2021 19:05:14 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamproc1-he-de.apache.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.2, HTML_OBFUSCATE_05_10=0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamproc1-he-de.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-he-de.apache.org ([116.203.227.195]) by localhost (spamproc1-he-de.apache.org [116.203.196.100]) (amavisd-new, port 10024) with ESMTP id MPZhtP8KWBL6 for ; Mon, 11 Jan 2021 19:05:13 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2607:f8b0:4864:20::434; helo=mail-pf1-x434.google.com; envelope-from=jjrushford@gmail.com; receiver= Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) by mx1-he-de.apache.org (ASF Mail Server at mx1-he-de.apache.org) with ESMTPS id A014B7FBFD for ; Mon, 11 Jan 2021 19:05:13 +0000 (UTC) Received: by mail-pf1-x434.google.com with SMTP id m6so519465pfk.1 for ; Mon, 11 Jan 2021 11:05:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ciLgVb2ixztLvP+V+z7Q9uU52DXUZbkZMgJJ6ASAqPo=; b=kNbVkT31Pmehuml3JJi+zG0JPTwjV2AyxzqZSY6XWRakyKrdkNfMzb6SfVpkgMw8lW AM3sE9XYoFEDviliq99OJur1E5t34O4+oWaiUA3udXS6KB/ndydxRISIrsFO01yaM1kK 2uv7vNu/afZLrehM0eZzaxVl8MfyxkVrmFRXCkrIwPHFUO0JvRZkatNLHFRh9W6CvFfd hM1nC48JhOGzqtlK5zKMZ2sfcqDI1wbaKhc5Pef8qnUGPvIKjA6QA0fojOELvm0WZFQz Bnxy3wfTEXq5imwvXZujkKYz6Cve7NskL3xR9S4vR0tMXB9kMRxIYJwCrRldUVRjbZWI mxrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ciLgVb2ixztLvP+V+z7Q9uU52DXUZbkZMgJJ6ASAqPo=; b=gbbciolP0aYjT/SRC1jo+ilud1oChjS/Mihbqx37OWfknSETi91i2Xbtk1NnMvflYv bs/V/0bDCKMuNKWmkEE3P6rZ2Dm8xmCXt9yJmvvrczY9bn1NCe/i9CcDv/2Bs8CpANvY thrffhW7Rf5SApGe7cQQFGZnhn3QeQ1GC1Y+hC8Qrokln50+LXK0E9XJKZ7jkM+0hI8K 3L+U5spCryUFNASX/oEf3TZhJZlDOeEsQlkZsmkVVedJZ1kEmiTns8bFSX+QfXGxndND ZYFEuNVcvoetVwM67steC+pqunSUBDWZllfH9RuwPnAcMIrGMdxcsa1n1G4NnnjhHIiA XFeg== X-Gm-Message-State: AOAM5315J2v6S21UNaB3e+T4qJRDcT4X0MEsXgJSAtudyX3+HOj0uujN aocSuYgQI8BDBDcD2aqmn6P9Bx16dI/xEEQXJfKBnwDQ X-Google-Smtp-Source: ABdhPJzTgJo3+zSknTjB/uP4XxaZv9jHgpBNZpH9SenCRW3xtyWxZdIKwpGz0CxrVcJ6O6kFE5kfXHNtu1SRDy86jBE= X-Received: by 2002:aa7:8c13:0:b029:1a1:e39e:dc29 with SMTP id c19-20020aa78c130000b02901a1e39edc29mr1039509pfd.64.1610391909512; Mon, 11 Jan 2021 11:05:09 -0800 (PST) MIME-Version: 1.0 References: <861F5E44-1EE3-45E6-83C5-584C215DDE9E@vecima.com> <971D6D9F-BA81-46D9-A2D1-31EC61AF84E9@apache.org> In-Reply-To: <971D6D9F-BA81-46D9-A2D1-31EC61AF84E9@apache.org> From: John Rushford Date: Mon, 11 Jan 2021 12:05:07 -0700 Message-ID: Subject: Re: Question about parent.config To: Mailing-List trafficserver Cc: Nick Dunkin Content-Type: multipart/alternative; boundary="000000000000b73af005b8a495cd" --000000000000b73af005b8a495cd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Leif is correct, you should look at using the cache_key plugin to generate a string that is used to lookup parents from it's hash. With that said, the string is hashed as is the path string and the hash is used to lookup parents. If you're trying to select specific parents based upon some path element that is not supported. On Mon, Jan 11, 2021 at 11:26 AM Leif Hedstrom wrote: > > > On Jan 11, 2021, at 11:22 AM, Nick Dunkin wrote: > > Hi all, > > I wish to use parent.config to control parent selection based on path > elements in the client URL. I know this is possible with the *url_regex*= primary > qualifier, however my question is as follows: > > The URL path element in question will be in the client request URL *but* = will > be dropped (by a custom plugin) from the URL before the request is made t= o > the parent. Does anybody know if the *url_regex *qualifier applies to > the full original client URL, or to the URL that is imminently about to = be > pulled from the parent. If it=E2=80=99s the latter and there=E2=80=99s a= nything I can do > in the custom plug-in to make this work more as I would like it, then > please let me know. > > > > Should be on the URL as it goes to the origin. But, I think (as of ATS > 9.0.x?) that you can use the cache_key plugin to change the effective URL > that is being used for parent selection? I haven=E2=80=99t tested / playe= d with > that though, John and Vijay might know? > > =E2=80=94 Leif > > --=20 John Rushford jjrushford@gmail.com --000000000000b73af005b8a495cd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Leif is correct, you should look at using the cache_key pl= ugin to generate a string that is used to lookup parents from it's hash= .=C2=A0 With that said, the string is hashed as is the path string and the = hash is used to lookup parents.=C2=A0 If you're trying to select specif= ic parents based upon some path element that is not supported.=C2=A0=C2=A0<= /div>
O= n Mon, Jan 11, 2021 at 11:26 AM Leif Hedstrom <zwoop@apache.org> wrote:


On Jan 11, 2021, at 11:22 AM= , Nick Dunkin <Nick.Dunkin@vecima.com> wrote:

= Hi all,
=C2=A0
I wish to use parent.config to control parent selection based on path= elements in the client URL.=C2=A0 I know this is possible with the= =C2=A0url_regex=C2=A0primary qualifier, however = my question is as follows:
=C2=A0
The URL = path element in question will be in the client request URL=C2=A0but=C2=A0will be dropped (by a custom plugin) from th= e URL before the request is made to the parent.=C2=A0 Does anybody know if = the=C2=A0url_regex=C2=A0qualifier applies = to the full original client URL, =C2=A0or to the URL that is imminently abo= ut to be pulled from the parent.=C2=A0 If it=E2=80=99s the latter and there= =E2=80=99s anything I can do in the custom plug-in to make this work more a= s I would like it, then please let me know.


Should be on the URL as it goes to the = origin. But, I think (as of ATS 9.0.x?) that you can use the cache_key plug= in to change the effective URL that is being used for parent selection? I h= aven=E2=80=99t tested / played with that though, John and Vijay might know?=

=E2=80=94 Leif



--
John Rushford
jjrushford@gmail.com
--000000000000b73af005b8a495cd--