one of the recurring issues we've seen is with people who
want rotatelogs to do its thing at midnight *local* time.
easily enough done with the offset argument -- but that
gets messy around the daylight savings issues.
the attached patch adds the '-l' option, which causes the
interval to be
Rodent of Unusual Size wrote:
the attached patch adds the '-l' option, which causes the
interval to be interpreted as local system time without
the user having to figure out nor change the offset.
See also
http://issues.apache.org/bugzilla/show_bug.cgi?id=24417
(I haven't reviewed any of the
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
Neil Gunton wrote:
Is this really such a special case? I can't believe nobody else has
wanted to implement a server like this.
It's a special case in the context of all of the servers, proxies,
transparent proxies and browsers together out there on the net - it's
useful to take off the load of
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
Hi all,
I have just installed the latest published version of httpd (v2.0.49),
and the problem where httpd refuses to start unless the file
ssl_gcache_data is manually deleted beforehand is still there.
I recall some recent discussion about the problem, but don't know if a
fix ever got into
Rather just use URL parameters. As I recall RFC2616 does not consider
a
request with a different cookie a different variant, so even if you
patch your server to allow it to differentiate between cookies,
neither
the browsers nor the transparent proxies in the path of the request
will
do what
Roy T. Fielding wrote:
I do wish people would read the specification to refresh their memory
before summarizing. RFC 2616 doesn't say anything about cookies -- it
doesn't have to because there are already several mechanisms for marking
a request or response as varying. In this case
Vary:
Hi all,
Following some questions on the apache-modules list, I whipped up a
quick module for Apache 2.0 to hopefully demonstrate how it's done. I'm
including the module code below: please tell me whether I'm smoking
crack before I post this on apache-modules.
Thanks for your thoughts,
Sander
On May 4, 2004, at 8:49 PM, Sander Temme wrote:
Hi all,
Following some questions on the apache-modules list, I whipped up a
quick module for Apache 2.0 to hopefully demonstrate how it's done.
I'm including the module code below: please tell me whether I'm
smoking crack before I post this on
Cliff Woolley wrote:
On Mon, 5 Apr 2004 [EMAIL PROTECTED] wrote:
stas2004/04/04 21:35:21
Modified:perl-framework/Apache-Test/lib/Apache TestRun.pm
TestConfig.pm
perl-framework/Apache-Test Changes
Log:
Don't try to set ulimit unlimited for
11 matches
Mail list logo