AUR web interface

Tasklist

FS#20071 - AUR site does not disable browser caching for returned files (eg. PKGBUILD)

Attached to Project: AUR web interface
Opened by Jaroslaw Rosiek (phi) - Sunday, 04 July 2010, 07:53 GMT
Last edited by Lukas Fleischer (lfleischer) - Friday, 21 January 2011, 15:00 GMT
Task Type Bug Report
Category Web Sites
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
AUR site does not disable browser caching for returned files. I've noticed this problem for PKGBUILD files.

Steps to reproduce:
1. Upload new package with version 1.0-1.
2. On the package page click PKGBUILD link (firefox will simply display its content)
3. Upload the same package but with version changed, let's say 1.0-2
4. Click on the same link as above -> old PKGBUILD content is displayed (cached!). Refresh browser -> new content is displayed.

Notes:
I think this may be the case also for other kinds of artifacts.
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Friday, 21 January 2011, 15:00 GMT
Reason for closing:  Not a bug
Additional comments about closing:  This is not a bug as it's a web server configuration issue (see comment). Disabled caching for packages in [unsupported] (on aur.archlinux.org) tho.
Comment by Lukas Fleischer (lfleischer) - Tuesday, 12 October 2010, 11:04 GMT
Hm, even tho I don't really get the problem with cached PKGBUILDs (you should always download and extract the source tarball to build packages and never copy and paste PKGBUILDs from the browser), this can be easily "fixed" by enabling either mod_headers or mod_expires and putting a ".htaccess" file, which sets the "Cache-Control" header, in the incoming dir. Sample attached.
   .htaccess (0.2 KiB)

Loading...