trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ethan Lai <yz...@yahoo.com>
Subject Re: Request URL unexpectedly changed to CacheUrl if CacheUrl is Set then Get
Date Fri, 29 Nov 2013 16:30:21 GMT
Jira ticket [TS-2410] EffectiveUrl infected if TSHttpTxnCacheLookupUrlGet
called after TSCacheUrlSet <https://issues.apache.org/jira/browse/TS-2410>filed

Test plugin which shows EffectiveUrl

   1. before CacheUrlSet
   2. after CacheUrlSet
   3. after TSHttpTxnCacheLookupUrlGet

attached in ticket.

EffectiveUrl = 'http://www.example.com/index.html' before CacheUrlSet
> EffectiveUrl = 'http://www.example.com/index.html' after CacheUrlSet
> EffectiveUrl = 'http://www.example.com/index.html*+infected*' after
> TSHttpTxnCacheLookupUrlGet



Thanks,
-Ethan


2013/11/28 Ethan Lai <yzlai@yahoo.com>

> Guys,
>
> I'm writing a plugin to append some value to CacheUrl with specify HTTP
> header.
> It works fine if I only call TSCacheUrlSet().
>
> However, if I call TSHttpTxnCacheLookupUrlGet() thereafter, the request
> URL will be modified to that CacheUrl I've set.
>
> IMHO, the original request URL should not be affected by CacheUrl,
> especially if I just get it back.  Any ideas?
>
> Scenario without calling TSHttpTxnCacheLookupUrlGet:
>    Origin Request URL: http://www.example.com/a
>    CacheUrl: http://www.example.com/abc
>    Expect Request URL: [Same as Origin Request URL]
>    Actual Request URL: [Same as Origin Request URL]
>
> Scenario with calling TSHttpTxnCacheLookupUrlGet:
>    Origin Request URL: http://www.example.com/a
> *   CacheUrl: http://www.example.com/a <http://www.example.com/a>bc*
>    Expect Request URL: [Same as Origin Request URL]
> *   Actual Request URL: http://www.example.com/a
> <http://www.example.com/a>bc*
>
> Thanks,
> -Ethan
>

Mime
View raw message