Re: apache 2 expiresdefault

[Jake Ravenwood <jakeravenwood@yahoo.com>]

you are saying that if i have the rewrite section added like below, and a request comes in, cache and proxy servers will  treat them different?  say if proxy server has a cache copy of www.mydomain.com,  rewriting it to www.mydomain.com/newindex.html will display the new page and not the cached one?



> In the mean time, if you really need a resolution you can
> use
> mod_rewrite and do something like
> 
> 
> 
> RewriteEngine On
> 
> RewriteRule ^/$ /index.html [R,L]
> 
> 
> 
> This will force the URI to change from
> http://www.example.com to
> http://www.example.com/index.html which are different
> requests from the
> caches perspective.? I just wouldn't suggest keeping
> that there for
> longer then you expect everyones cache to update.
> 
> 
> 
> --Michael
> 
> 
>  
> 
> 
>  
> 
> -----Original Message-----
> From: Jake Ravenwood <jakeravenwood@yahoo.com>
> To: linux-admin@vger.kernel.org
> Sent: Wed, 9 Jul 2008 1:02 pm
> Subject: Re: apache 2 expiresdefault
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> I am still looking on how to have their browsers/proxy
> server to refresh soon. 
> or trick their browser that there is new content already so
> they need to get the 
> new copy. 
> 
> i am thinking of changing the directoryindex and point to
> index.php -such that 
> it changes the inode,mtime and filesize.  then inside
> index.php i have:
> <?
> header("Cache-Control: no-store, no-cache,
> must-revalidate");
> header("Cache-Control: post-check=0,
> pre-check=0", false);
> header("Pragma: no-cache"); 
> 
> call_the_original_html_file. 
> 
> ?>
> 
> how to i call the original html file from index.php?  i
> mean, index.php will 
> load first then it will call/load html file.
> 
> 
> thanks,
> jake
> 
> 
> 
> --- On Wed, 7/9/08, Hubert Grzeskowiak
> <linux-admin-ml@nemesis13.de> wrote:
> 
> > From: Hubert Grzeskowiak
> <linux-admin-ml@nemesis13.de>
> > Subject: Re: apache 2 expiresdefault
> > To: 
> > Date: Wednesday, July 9, 2008, 4:17 AM
> > Glynn Clements wrote:
> > > Jake Ravenwood wrote:
> > > 
> > >> i have a linux/apache2 newly setup. i put it
> > online last week but
> > >> after a day, i got a lot of email/phone
> complaints
> > saying they are
> > >> seeing old pages/old contents of the site. My
> site
> > changes
> > >> frequently(daily). after checking i found
> that
> > apache has
> > >> ExpiresDefault A2419200 which spells to
> 28days. I
> > changed it to
> > >> ExpiresDefault A0 and reload Apache. Some
> > end-users are now seeing the
> > >> new content but some are still seeing the old
> > pages. What else i
> > >> missed?
> > > 
> > > If someone already has a cached version with the
> > 28-day expiry, their
> > > web browser (or an intermediate proxy) is likely
> to
> > keep using it
> > > until it expires or until they force a reload.
> Nothing
> > you do to your
> > > web server can force those existing copies to
> expire
> > prematurely.
> > > 
> > 
> > hi Jake,
> > try adding those meta tags to your (x)html files (into
> the
> > head part of 
> > course):
> > 
> >   <meta http-equiv="expires"
> > content="-1">
> >   <meta http-equiv="pragma"
> > content="no-cache">
> >   <meta http-equiv="cache-control"
> > content="no-cache">
> > 
> > this won't force your clients to reload the page,
> but
> > it should suppress 
> > future caching. it's just html, so sure not every
> > browser will interpret 
> > that.
> > --
> > To unsubscribe from this list: send the line
> > "unsubscribe linux-admin" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at 
> > http://vger.kernel.org/majordomo-info.html
> 
> 
>       
> 
> --
> To unsubscribe from this list: send the line
> "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at 
> http://vger.kernel.org/majordomo-info.html