Paul,

I see nothing wrong with the url_regex you're using, it should work.  Try
enabling debug in records.config with a debug string of "parent_select".
Then run you're test and look to see if the url_regex line matches.  You'll
see something like this in traffic.out:

[Dec 20 16:20:48.271] Server {0x2aff9d17f700} DEBUG:
<ParentSelection.cc:701 (UpdateMatch)> (parent_select) Matched with
0x13c3db8 parent node from line 4
[Dec 20 16:22:16.064] Server {0x2ba96742a700} DEBUG:
<ParentSelection.cc:701 (UpdateMatch)> (parent_select) Matched with
0x1dedd58 parent node from line 5

You may see multiple matches.  The first match is used, smaller line number.

regards
John

On Thu, Dec 8, 2016 at 7:38 AM, Paul Kingsnorth <
[email protected]> wrote:

> Hi, I’m looking at parent caching in Traffic Server 7.0.0 (operating in
> forward proxy mode). I’ve got the basic configuration done – I’ve set this
> in records.config:
>
>          CONFIG proxy.config.http.parent_proxy_routing_enable INT 1
>
> and added a line like this to parent.config:
>
>         dest_domain=.   parent=”<ip-address>:8080”
>
> and every request is now being sent to the parent, as required.
>
>
>
> I’m now trying to bypass the parent for some URLs but I haven’t yet
> managed to get this to work. For example, to bypass the parent cache for
> the URL http://www.xyzzy.com/images/fred.gif I’ve tried adding the
> following the parent.config:
>
>         url_regex=.*xyz.* go_direct=true
>
> but the request still goes to the parent instead of going directly to the
> origin server.
>
>
>
> Does anyone have any examples of using url_regex in parent.config to
> bypass the parent cache?
>
>
>
> Thanks, Paul
>
>
>
>
>
>
>
> *Paul Kingsnorth Principal Software Engineer *[image: Telephone] +44 118
> 903 8649 <+44%20118%20903%208649>
> [image: Twitter]@clearswift
>
> [image: Clearswift] <http://www.clearswift.com/>
>
> 1310 Waterside | Arlington Business Park | Theale | Berkshire | RG7 4SA |
> United Kingdom
>
> RELEASED: Clearswift v4.5 Gateways. Upgrade to the latest Clearswift
> technology today. Learn more *here.*
> <https://www.clearswift.com/training-and-support/migration-and-upgrades>
>
> Clearswift HQ will be closed for the festive period from 1pm GMT on Friday
> 23rd December and will reopen at 9am GMT Wednesday 28th December. The
> Clearswift team will be processing orders during this period but to ensure
> your order is processed in time, we request you send your orders to
> [email protected] as soon as possible.  We take the
> opportunity to wish you a safe and joyous holiday period.
>
> This e-mail and any files transmitted with it are strictly confidential,
> may be privileged and are intended only for use by the addressee unless
> otherwise indicated.  If you are not the intended recipient any use,
> dissemination, printing or copying is strictly prohibited and may be
> unlawful.  If you have received this e-mail in error, please delete it
> immediately and contact the sender as soon as possible.  Clearswift cannot
> be held liable for delays in receipt of an email or any errors in its
> content. Clearswift accepts no responsibility once an e-mail and any
> attachments leave us. Unless expressly stated, opinions in this message are
> those of the individual sender and not of Clearswift.
>
> This email message has been inspected by Clearswift for inappropriate
> content and security threats.
>
> To find out more about Clearswift’s solutions please visit
> www.clearswift.com
>



-- 
John Rushford
[email protected]

Reply via email to