Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 79702 invoked from network); 23 Sep 2004 17:52:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 23 Sep 2004 17:52:14 -0000 Received: (qmail 60556 invoked by uid 500); 23 Sep 2004 17:54:04 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 60393 invoked by uid 500); 23 Sep 2004 17:54:02 -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: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 60282 invoked by uid 99); 23 Sep 2004 17:54:01 -0000 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=DNS_FROM_RFC_ABUSE,FROM_ENDS_IN_NUMS,RCVD_IN_RFC_IPWHOIS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [144.160.112.18] (HELO tspsmtp8.sbc.com) (144.160.112.18) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 23 Sep 2004 10:54:00 -0700 Received: from sbc.com (localhost [127.0.0.1]) by tspsmtp8.sbc.com (8.12.10/8.12.10) with ESMTP id i8NHrsVJ022881; Thu, 23 Sep 2004 12:53:54 -0500 (CDT) Received: from MOSTLS1MSGHUB03.ITServices.sbc.com (mostls1msghub03.itservices.sbc.com [132.201.19.8]) by tspsmtp8.sbc.com (8.12.10/8.12.10) with ESMTP id i8NHrodd022847; Thu, 23 Sep 2004 12:53:50 -0500 (CDT) Received: from MOSTLS1MSGUSR12.ITServices.sbc.com ([132.201.19.63]) by MOSTLS1MSGHUB03.ITServices.sbc.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 23 Sep 2004 12:53:50 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 23 Sep 2004 12:53:49 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [users@httpd] mod_expire Thread-Index: AcShlJuoSrjAWZkvQseGiPO75HxR7QAAS92g From: "PINNI, BALANAND \(SBCSI\)" To: , "Joshua Slive" X-OriginalArrivalTime: 23 Sep 2004 17:53:50.0541 (UTC) FILETIME=[486BD7D0:01C4A196] X-Virus-Checked: Checked Subject: RE: [users@httpd] mod_expire X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Thanks Joshu How to set THIS DIRECTIVE FOR 24 Hrs. How is he getting A2592000 value for a month? # expire GIF images after a month in the client's cache ExpiresByType image/gif A2592000 # HTML documents are good for a week from the # time they were changed ExpiresByType text/html M604800=20 ExpiresByType Directive Description: Value of the Expires header configured by MIME type=20 Syntax: ExpiresByType MIME-type seconds=20 Context: server config, virtual host, directory, .htaccess=20 Override: Indexes=20 Status: Extension=20 Module: mod_expires=20 This directive defines the value of the Expires header and the max-age directive of the Cache-Control header generated for documents of the specified type (e.g., text/html). The second argument sets the number of seconds that will be added to a base time to construct the expiration date. The Cache-Control: max-age is calculated by subtracting the request time from the expiration date and expressing the result in seconds. The base time is either the last modification time of the file, or the time of the client's access to the document. Which should be used is specified by the field; M means that the file's last modification time should be used as the base time, and A means the client's access time should be used. The difference in effect is subtle. If M is used, all current copies of the document in all caches will expire at the same time, which can be good for something like a weekly notice that's always found at the same URL. If A is used, the date of expiration is different for each client; this can be good for image files that don't change very often, particularly for a set of related documents that all refer to the same images (i.e., the images will be accessed repeatedly within a relatively short timespan). Example: # enable expirations ExpiresActive On # expire GIF images after a month in the client's cache ExpiresByType image/gif A2592000 # HTML documents are good for a week from the # time they were changed ExpiresByType text/html M604800=20 24HRS: -----Original Message----- From: Joshua Slive [mailto:jslive@gmail.com]=20 Sent: Thursday, September 23, 2004 12:40 PM To: users@httpd.apache.org Subject: Re: [users@httpd] mod_expire On Thu, 23 Sep 2004 11:55:13 -0500, PINNI, BALANAND (SBCSI) wrote: > Dear Gurus, >=20 > Can anyone give me direction as to how to use this directives? I need > for 24Hrs. > Details about it can be found at: > http://httpd.apache.org/docs-2.1/mod/mod_expires.html > Else please help me if anyone of you have set this in your > configuration. Sure, lots of people use this. What exactly is your question? What is it about the documentation that you don't understand? Here's an example: ExpiresActive On ExpiresDefault "access plus 24 hours" > Also, should the cache be enabled in httpd.conf? No, mod_cache is independent of mod_expires. They do completely different things. One tells the clients how long to cache for, the other does caching at the server level. 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 --------------------------------------------------------------------- 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