[squid-users] Force the caching of 302 responses without Expires header.[squid 2.5]

Hi
Is there some workaround to have squid cache 302 responses that do not have
Expire header.[squid is acting as a web proxy]

FAQs are saying 'A 302 Moved Temporarily response is cachable ONLY if the
response also includes an *Expires* header.'. I could not find any
refresh_pattern that would help me do
that.

I a newbie with squid. Here I some options that I can think of: a) write
some Refresh Pattern, or b) Fool Squid into believing that it did get an
Expire header, or c) Some plugin for Squid?

I would appreciate any pointers.

I need it for internal load testing of my application. I am hoping that I
can cache the both 302 and
200 headers without actually repeatedly hitting the real webservers.

Thanx,
HB

squid -v
Squid Cache: Version 2.5.STABLE12
configure options: --prefix=/usr --exec_prefix=/usr --bindir=/usr/sbin
--sbindir=/usr/sbin --libexecdir=/usr/lib/squid --sysconfdir=/etc/squid
--localstatedir=/var/spool/squid --datadir=/usr/share/squid
--enable-async-io --with-pthreads --enable-storeio=ufs,aufs,diskd,null
--enable-linux-netfilter --enable-arp-acl --enable-removal-policies=lru,heap
--enable-snmp --enable-delay-pools --enable-htcp --enable-poll
--enable-cache-digests --enable-underscores --enable-referer-log
--enable-useragent-log --enable-auth=basic,digest,ntlm --enable-carp
--with-large-files i386-debian-linux
Received on Mon Jan 01 2007 - 10:26:46 MST