@DrDaveD but I am still lost this header Cache-control: max-age who is responsible for setting it up the client (the curl) or the (xrootd http server). I tried this without much luck:

efajardo@uaf-7 ~$http_proxy="http://cvmfs-1.t2.ucsd.edu:3128" curl -H "Cache-Control: max-age=86400" -v http://stashcache.t2.ucsd.edu:8000/user/dweitzel/public/blast/queries/query1 -O
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* About to connect() to proxy cvmfs-1.t2.ucsd.edu port 3128 (#0)
*   Trying 169.228.130.85...
* Connected to cvmfs-1.t2.ucsd.edu (169.228.130.85) port 3128 (#0)
> GET http://stashcache.t2.ucsd.edu:8000/user/dweitzel/public/blast/queries/query1 HTTP/1.1
> User-Agent: curl/7.29.0
> Host: stashcache.t2.ucsd.edu:8000
> Accept: */*
> Proxy-Connection: Keep-Alive
> Cache-Control: max-age=86400
> 
< HTTP/1.1 200 OK
< Content-Length: 103
< Date: Tue, 22 Oct 2019 16:54:31 GMT
< X-Cache: MISS from cvmfs-1.t2.ucsd.edu
< Via: 1.1 cvmfs-1.t2.ucsd.edu (squid/frontier-squid-4.4-2.1.osg34.el7)
< Connection: keep-alive
< 
{ [data not shown]
100   103  100   103    0     0  10200      0 --:--:-- --:--:-- --:--:-- 11444
* Connection #0 to host cvmfs-1.t2.ucsd.edu left intact```

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.