Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of abiacco@formatdynamics.com
 designates 209.111.94.85 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: cache POST requests
Date: Tue, 10 Feb 2009 11:52:28 -0700
Message-ID: 
 <40D5E3C3CBE03D45A776E7C358BDE908E3855A@missoula.formatdynamics.com>
In-Reply-To: <A84920684DBB3746A1BEA1296EC9E4EB0324F17B@EXCVSRV2.aoins.com>
Thread-Topic: cache POST requests
Thread-Index: AcmLrOuQA9xhE3xqR/uvHHwlPK8w/wAAH2cAAABYBhA=
References: 
 <40D5E3C3CBE03D45A776E7C358BDE908E3854D@missoula.formatdynamics.com>
 <A84920684DBB3746A1BEA1296EC9E4EB0324F17B@EXCVSRV2.aoins.com>
From: "Anthony J. Biacco" <abiacco@formatdynamics.com>
To: <modules-dev@httpd.apache.org>

I read that for the 1.0 spec, but thought for the 1.1 it was possible
with the proper expiration headers. Although I do understand the keying
problem.
My problem is that my POSTs vary wildly in size from 5k to over a meg,
and avg. out to about 45k. Being that GETs in apache by default are
limited to 8k, I'll get a 414 error, so I'm not sure where I can turn to
cache this. I suppose I can up the LimitRequestLine parameter to the max
I need, but I'm not sure how kosher that is.

Thanx,

-Tony
---------------------------
Manager, IT Operations
Format Dynamics, Inc.
303-573-1800x27
abiacco@formatdynamics.com
http://www.formatdynamics.com


-----Original Message-----
From: Houser, Rick [mailto:Houser.Rick@aoins.com]=20
Sent: Tuesday, February 10, 2009 11:37 AM
To: modules-dev@httpd.apache.org; users@httpd.apache.org
Subject: RE: cache POST requests

You really shouldn't be trying to cache responses to post requests.
Completely from memory, but the HTTP spec says not to cache post
responses.  The URI is the base key to any caching implementations (with
the addition of a select few vary headers, etc.), and your post data
really doesn't factor in.

The normal pattern to use in most of these situations is
http://en.wikipedia.org/wiki/Post/Redirect/Get.  Think of a post as a
submission from the client.  Once you have that submission, just tell
the client where to get the appropriate resource with a GET request and
leave the heavy lifting/caching until that request comes in.


Thanks,

Rick Houser
Auto-Owners Insurance
Systems Support
(517)703-2580

-----Original Message-----
From: Anthony J. Biacco [mailto:abiacco@formatdynamics.com]=20
Sent: Tuesday, February 10, 2009 1:25 PM
To: users@httpd.apache.org
Cc: modules-dev@httpd.apache.org
Subject: cache POST requests

Hello,

I'm using apache 2.2.11 on centos 5/x86_64 I'm testing out caching data
for GET requests using mod_disk_cache, which I have working.
I'd also like to cache data for the same requests via the POST method,
but this doesn't seem to work.
Is this supported? If so, is there any config changes required for this
to work? If not, is this feature planned?

Thanx,

-Tony
---------------------------
Manager, IT Operations
Format Dynamics, Inc.
303-573-1800x27
abiacco@formatdynamics.com
http://www.formatdynamics.com