Plüm, Rüdiger, VF-Group wrote:
Can you try with the following additional patch and a clean cache?
Afterwards there should only be very very few orphaned header files
left.:
Index: modules/cache/mod_disk_cache.c
===
---
Ruediger Pluem wrote:
What information do your cookies contain? Are these session cookies that
are individual to each client? In this case the usage of mod_disk_cache
with Vary Cookies set would be bad. As these responses would be individual
you couldn't reuse the results anyway for other
I posted this on the users list, but was advised to post it to dev as
well, since it seemed relevant to developers. Hope that's ok...
I am using Apache 2.2.9 on Linux AMD64, built from source. There is one
server running two builds of Apache - a lightweight front-end caching
reverse proxy
[EMAIL PROTECTED] wrote:
If this fellow were to simply 'stuff' his Cookie into the
'extra text' part of the User-Agent: string and send
out a Vary: User-Agent along with the response
then it would actually work the way he expects it too.
Thanks to Roy and Kevin for your insight. Sorry if this
[EMAIL PROTECTED] wrote:
Bottom line:
In order to do your 'Cookie' scheme and have it work with
all major browsers you might have to give up on the idea
that the responses can EVER be 'cached' locally by
a browser... but now you also lose the ability to have
it cached by ANYONE.
There
[EMAIL PROTECTED] wrote:
MOST Proxy Cache Servers ( including ones that SAY they are
HTTP/1.1 compliant ) do NOT handle Vary: and they will simple
treat ANY response they get with a Vary: header of any kind
exactly the way MSIE seems to. They will treat it as if it was
Vary: * ( Vary: STAR )
Graham Leggett wrote:
I would disagree - if a proxy on the net cached every variant of every
page simply based on a cookie header, there would so many different
variants of the same page in the cache that from a system resource
perspective the cache might as well not be there. Cookies only
Graham Leggett wrote:
There is already a mechanism for caching different variants of a page -
simply encode the info into the URL. This is supported on all browsers
and cannot be switched off through user preference (as cookies can).
Because a mechanism already exists, there isn't much point
Graham Leggett wrote:
Neil Gunton wrote:
The problem now is that the browsers (IE and Mozilla at least) don't
seem to differentiate requests based on cookies. I have tested
requesting a page with a certain cookie (where the page has a sufficient
expiration to warrant being cached
? Or, will this be included in either future
versions of mod_proxy or the equivalent module in Apache 2.x? Any
insights greatly appreciated.
Thanks,
-Neil Gunton
Neil Gunton wrote:
Hi all,
I apologise in advance if this is obvious or otherwise been answered
elsewhere, but I can't seem to find any reference to it.
I am using Apache 1.3.29 with mod_perl, on Linux 2.4. I am running
mod_proxy as a caching reverse proxy front end, and mod_perl
11 matches
Mail list logo
