Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make sage -upgrade work with caching proxy servers #2044

Closed
sagetrac-mabshoff mannequin opened this issue Feb 4, 2008 · 4 comments
Closed

make sage -upgrade work with caching proxy servers #2044

sagetrac-mabshoff mannequin opened this issue Feb 4, 2008 · 4 comments

Comments

@sagetrac-mabshoff
Copy link
Mannequin

sagetrac-mabshoff mannequin commented Feb 4, 2008

In http://groups.google.com/group/sage-devel/t/e88f02da4c345cb7 Phil reports the following problem:

Hello,

I had many troubles getting the upgrade through a caching proxy on
which I've no control.
When running sage -upgrade, the proxy didn't let me getting the latest
versions, which made troubles with the critical files:
http://www.sagemath.org/packages/standard/list
http://www.sagemath.org/packages/standard/deps
http://www.sagemath.org/packages/standard/newest_version
http://www.sagemath.org/packages/standard/README
http://www.sagemath.org/packages/install

I could get around by providing manually the files and skipping the
download in local/bin/sage-update

But would it be possible to add some anti-caching headers to the
official sage server for those files?
It'd help a lot all people like me with a sage install behind caching
proxy.
Sth like:
 Expires: Mon, 26 Jul 1997 05:00:00 GMT"
 Cache-Control: no-store, no-cache, must-revalidate"
 Cache-Control: post-check=0, pre-check=0", false
 Pragma: no-cache

Phil 

Component: website/wiki

Reviewer: Lorenz Panny

Issue created by migration from https://trac.sagemath.org/ticket/2044

@sagetrac-mabshoff sagetrac-mabshoff mannequin added this to the sage-5.11 milestone Feb 4, 2008
@sagetrac-mabshoff sagetrac-mabshoff mannequin self-assigned this Feb 4, 2008
@sagetrac-mabshoff
Copy link
Mannequin Author

sagetrac-mabshoff mannequin commented Feb 8, 2008

comment:1

Some more info from Phil:

Apparently your server is an Apache so after googling myself I found
those pages:
http://www.askapache.com/htaccess/speed-up-sites-with-htaccess-cachin...
http://httpd.apache.org/docs/2.0/mod/mod_expires.html
http://httpd.apache.org/docs/2.0/mod/mod_headers.html#header
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9

So I guess having a .htaccess in packages/ with sth like that is good
enough
(be sure to have modules expire and headers and to allow .htaccess
files)
<FilesMatch "(list|deps|newest_version|README)$">
<IfModule mod_expires.c>
  # any Expires Directives go here
  ExpiresActive On
  ExpiresDefault access
</IfModule>
<IfModule mod_headers.c>
  # any Header directives go here
  Header set Cache-Control "no-store, no-cache, must-revalidate, max-
age=0"
  Header set Pragma "no-cache"
</IfModule>
</FilesMatch>

And same for ../install

To be tested with sth like:
 wget -O /dev/null -S http://www.sagemath.org/packages/standard/list
to see the headers returned by the Apache server 

Cheers,

Michael

@jdemeyer jdemeyer modified the milestones: sage-5.11, sage-5.12 Aug 13, 2013
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.1, sage-6.2 Jan 30, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.2, sage-6.3 May 6, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.3, sage-6.4 Aug 10, 2014
@mkoeppe
Copy link
Member

mkoeppe commented Aug 26, 2021

comment:7

outdated, should close

@mkoeppe mkoeppe removed this from the sage-6.4 milestone Aug 26, 2021
@yyyyx4
Copy link
Member

yyyyx4 commented Aug 27, 2021

comment:8

Indeed, none of those URLs exist anymore (and we can assume that neither does the proxy).

@yyyyx4
Copy link
Member

yyyyx4 commented Aug 27, 2021

Reviewer: Lorenz Panny

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants