Call for Papers Opens for ApacheCon US 2007
The Call for Papers is now open for ApacheCon US, to be held November
12-16 at the Peachtree Westin, Atlanta. The conference will consist
of two day of tutorials (November 12-13) and three days of regular
conference sessions (November 14-16).
Pl
Nick Kew wrote:
On Fri, 13 Apr 2007 16:30:06 -0500
Andy Wang <[EMAIL PROTECTED]> wrote:
There are a number of potential workarounds (LocationMatch, or
Multiple Location blocks to deal with the ;* pattern) but it does
seem like this is a bug unless someone can clarify RFC 2396 section
3.3 for
On *April 16*, Rich Bowen wrote:
>
> Call for Papers Opens for ApacheCon US 2007
>
> The Call for Papers is now open for ApacheCon US, to be held November
> 12-16 at the Peachtree Westin, Atlanta. The conference will consist
> of two day of tutorials (November 12-13) and three days of regular
> c
On Apr 16, 2007, at 11:27, Eli Marmor wrote:
On *April 16*, Rich Bowen wrote:
Call for Papers Opens for ApacheCon US 2007
The Call for Papers is now open for ApacheCon US, to be held November
12-16 at the Peachtree Westin, Atlanta. The conference will consist
of two day of tutorials (Novembe
On 04/13/2007 05:31 PM, Niklas Edmundsson wrote:
> On Wed, 11 Apr 2007, Niklas Edmundsson wrote:
>
>> Looking a bit further, I think that something like this would actually
>> be enough:
>
>
>
> I have now tested this patch, and it seems to solve the problem. This is
> on httpd-2.2.4 + patch
mån 2007-04-16 klockan 22:58 +0200 skrev Ruediger Pluem:
> My first question in this situation is: What is the correct thing to do here?
> Generate the response from the cache (of course with the updated headers from
> the 304
> backend response) and delete the cache entry afterwards?
My underst
