Problem with Expires

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




	Hi Everybody,

I'm having some trouble setting up my Trac (trac.edgewall.org) server. I'm using apache and mod_python running Trac 0.11.6 over https, and everything seems to work fine. The only problem is that the Edit pages (when you click 'Edit this page') have the standard "access+1d" expiration, so if I try to edit the same page again I get the old, cached version of it, which obviously doesn't work.

I tried to manually change the expiration by adding the following to my
<Directory> block:

<Directory /var/www/html/project>
    SetHandler mod_python
    PythonInterpreter main_interpreter
    PythonHandler trac.web.modpython_frontend
    SetEnv PYTHON_EGG_CACHE /var/trac/eggs
    PythonOption TracEnv /var/www/html/project
    PythonOption TracUriRoot /project

    ExpiresActive On
    <FilesMatch ".*action=edit$">
      ExpiresDefault "access+1s"
      Header set Cache-control "no-cache"
    </FilesMatch>

    Order Allow,Deny
    Allow from all
    AuthType Basic
    AuthName "Project Trac"
    AuthUserFile /var/www/trac.htpasswd
</Directory>

But when I try to access an edit page I get the following HTTP headers:

https://xxx/yyy/wiki/Test/IncludePage4?action=edit

GET /yyy/wiki/Test/IncludePage4?action=edit HTTP/1.1
Host: external.lite3d.com
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.6) Gecko/20091216
Fedora/3.5.6-1.fc11 Firefox/3.5.6
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: trac_auth=222c8b1f1e7aed68429276a8a85adf97;
trac_form_token=7372191226417b9d5480ecaa;
__utma=188037116.136402090.1263196685.1266295477.1266548406.51;
__utmz=188037116.1266216773.47.5.utmcsr=zzz|utmccn=(referral)|utmcmd=referral|utmcct=/wiki/About;
PHPSESSID=u071vjsiu89vpjtqddkk683dh6; trac_form_token=54af8a56aa3664f8f238fc64;
__utmc=188037116; __utmb=188037116.35.10.1266548406

HTTP/1.x 200 OK
Date: Fri, 19 Feb 2010 02:27:07 GMT
Server: Apache/2.2.8 (Fedora)
Cache-Control: must-revalidate, max-age=86400
Content-Length: 7101
Expires: Sat, 20 Feb 2010 02:27:07 GMT
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html;charset=utf-8

Which have the same, wrong settings. :(

Can anybody give me a hint on what I might be doing wrong? How can I debug Expires rules to see if the rule is applied at all?

Any hints welcome

	Dirk

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx


[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux