Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 65394 invoked from network); 31 Oct 2006 16:37:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 Oct 2006 16:37:31 -0000 Received: (qmail 98506 invoked by uid 500); 31 Oct 2006 16:37:29 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 98484 invoked by uid 500); 31 Oct 2006 16:37:29 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 98467 invoked by uid 99); 31 Oct 2006 16:37:29 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Oct 2006 08:37:29 -0800 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of jslive@gmail.com designates 66.249.82.237 as permitted sender) Received: from [66.249.82.237] (HELO wx-out-0506.google.com) (66.249.82.237) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Oct 2006 08:37:04 -0800 Received: by wx-out-0506.google.com with SMTP id s19so2068139wxc for ; Tue, 31 Oct 2006 08:36:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=L3rkDZYggJjoH5ooYwLtqICTnz4+m2yG5bUigiCeZCitUtTF865G1zU7Lh/iFkXYto7bAM/6U7gZe9KuYH22vY2mThfX0mx6LfOMClj6CtqwR2hz4pGntCmvaP6/P14LRvRVoDUS/DbG2KH/ZcGwRj1djqcrZ40/6R2ETLdojos= Received: by 10.70.36.9 with SMTP id j9mr7529690wxj; Tue, 31 Oct 2006 08:36:39 -0800 (PST) Received: by 10.70.20.4 with HTTP; Tue, 31 Oct 2006 08:36:39 -0800 (PST) Message-ID: Date: Tue, 31 Oct 2006 11:36:39 -0500 From: "Joshua Slive" Sender: jslive@gmail.com To: users@httpd.apache.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Google-Sender-Auth: 3f45b2c3176dcb98 X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] Allowing negotiated content to be cached On 10/31/06, Spartanicus wrote: > I'm experimenting with multiviews to get more user friendly URLs, and so > that I can change "foobar.htm" to "foobar.cgi" without causing problems > or requiring a fix. > > Consequently normally the document returned should be the same so I > added "CacheNegotiatedDocs On" for HTTP/1.0 requests. > > What is the best way to allow these types of "negotiated" documents to > be cached as if they weren't negotiated for HTTP/1.1 requests? You need to examine exactly what response headers apache is sending for these requests and make adjustments as required. For example, you might find SetEnv force-no-vary or Header unset Vary might help. But I haven't tested that. Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org