On Oct 6, 2014, at 11:28 AM, Bill Zeng wrote:
> Hi James,
>
> Can you elaborate on the inconsistency problems a little bit more? To my
> understanding, traffic_cop runs as root. traffic_manager and traffic_server
> run as unprivileged nobody.
traffic_cop runs as root, traffic_manager retains pr
For evicting the cached version and forcing the request to be sent to
origin, he could do like what plugin
/plugins/experimental/regex_revalidate/ does, that is, on event
TS_EVENT_HTTP_CACHE_LOOKUP_COMPLETE, do TSHttpTxnCacheLookupStatusSet(txn,
TS_CACHE_LOOKUP_HIT_STALE);
Acácio Centeno
Software
Hi James,
Can you elaborate on the inconsistency problems a little bit more? To my
understanding, traffic_cop runs as root. traffic_manager and traffic_server
run as unprivileged nobody.
Thanks.
Bill
On Mon, Sep 29, 2014 at 10:57 AM, James Peach wrote:
> Hi all,
>
> I've been looking at the w
On Oct 6, 2014, at 10:56 AM, Brian Geffon wrote:
> James, I think the problem of requiring std::shared_ptr is that it wont
> work with some older compilers without adding --std=c++0x, such as g++ 4.4.x
In that case, I think you should check for what you need at build time and puke
if it is not
James, I think the problem of requiring std::shared_ptr is that it wont
work with some older compilers without adding --std=c++0x, such as g++ 4.4.x
Brian
On Mon, Oct 6, 2014 at 8:21 AM, James Peach wrote:
> On Oct 3, 2014, at 9:06 PM, Brian Geffon wrote:
>
> > Hey all,
> > So there is a weird
Hi Alan,
Thomas¹s requirement has two parts:
- Requests to URI /a are cached
- If condition x matched, requests to /a must bypass the cache and served
>From the origin without putting the response into the cache
>From what I understand, essentially, the use case is to force certain
client reque
On Oct 3, 2014, at 9:06 PM, Brian Geffon wrote:
> Hey all,
> So there is a weird situation we're in with the c++ api where it has a
> dependency on shared_ptr which can exist in memory or tr1/memory and
Just stop doing this. tr1 is ancient, so require std::shared_ptr in order to
build the C++ A
Monday, October 6, 2014, 4:51:12 AM, you wrote:
> - Requests to URI /a are cached
> - If condition x matched, requests to /a must bypass the cache and served
> from
> the origin without putting the response into the cache
Look TSHttpTxnServerRespNoStoreSet().
Saturday, October 4, 2014, 10:57:27 AM, you wrote:
> Make one of your public include files autoconf generated? Like we do for the
> C APIs definitions file.
Close, but I think what would be better is to combine this with Brian's
original thought.
So in Brian's shared pointer header, he has bas
To simple ... thank you!
Am Montag, 6. Oktober 2014, 14:29:04 schrieb Sudheer Vinukonda:
> You may want to checkout the API TSHttpTxnConfigIntSet that allows
> overriding the setting "proxy.config.http.cache.http".
>
> For example:
>
> TSHttpTxnConfigIntSet(txn, TS_CONFIG_HTTP_CACHE_HTTP, 0);
>
You may want to checkout the API TSHttpTxnConfigIntSet that allows
overriding the setting "proxy.config.http.cache.http".
For example:
TSHttpTxnConfigIntSet(txn, TS_CONFIG_HTTP_CACHE_HTTP, 0);
Thanks,
Sudheer
On 10/6/14, 2:51 AM, "Thomas Berger" wrote:
>Hi all,
>
>for one of our project
Hi all,
for one of our projects, we need to bypass the cache under specific conditions.
I found no way right now to set a request to non-cacheable in the plugin API
documentation.
`TSHttpTxnReqCacheableSet` does only force a request to be cachable.
Is there any way to enforce the following:
12 matches
Mail list logo
