You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2013/09/04 20:00:58 UTC

[jira] [Updated] (TS-2139) Twice purge to refresh object form cache when enable-interim-cache

     [ https://issues.apache.org/jira/browse/TS-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-2139:
------------------------------

    Fix Version/s: 5.0.0
    
> Twice purge to refresh object form cache when enable-interim-cache
> ------------------------------------------------------------------
>
>                 Key: TS-2139
>                 URL: https://issues.apache.org/jira/browse/TS-2139
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Cache
>            Reporter: bettydramit
>             Fix For: 5.0.0
>
>
> Centos x86_64 gitmaster and http://people.apache.org/~zwoop/rel-candidates/trafficserver-3.3.5-dev.tar.bz2
> when enable enable-interim-cache
> It muse use twice purge to refresh object form cache
> my records.config
> LOCAL proxy.config.cache.interim.storage STRING /dev/vdb
> Test example:
> [root@localhost trafficserver]# wget -SO /dev/null -e http_proxy=127.0.0.1 http://www.test.com/ben.bf
> --2013-08-17 14:45:23--  http://www.test.com/ben.bf
> Connecting to 127.0.0.1:80... connected.
> Proxy request sent, awaiting response... 
>   HTTP/1.0 200 OK
>   Date: Sat, 17 Aug 2013 06:38:13 GMT
>   Server: ATS/3.3.5-dev
>   Last-Modified: Mon, 08 Jul 2013 15:26:09 GMT
>   ETag: "41d26-103-4e101a9fc2c93"
>   Accept-Ranges: bytes
>   Content-Length: 259
>   Content-Type: text/plain; charset=UTF-8
>   Age: 430
> Length: 259 [text/plain]
> Saving to: “/dev/null”
> 100%[====================================================================================>] 259         --.-K/s   in 0s      
> 2013-08-17 14:45:23 (38.5 MB/s) - “/dev/null” saved [259/259]
> [root@localhost trafficserver]# curl -X purge -x 127.0.0.1:80 -v http://www.test.com/ben.bf          
> * About to connect() to proxy 127.0.0.1 port 80 (#0)
> *   Trying 127.0.0.1... connected
> * Connected to 127.0.0.1 (127.0.0.1) port 80 (#0)
> > purge http://www.test.com/ben.bf HTTP/1.1
> > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> > Host: www.test.com
> > Accept: */*
> > Proxy-Connection: Keep-Alive
> > 
> < HTTP/1.1 200 OK
> < Date: Sat, 17 Aug 2013 06:45:28 GMT
> < Proxy-Connection: keep-alive
> < Server: ATS/3.3.5-dev
> < Content-Length: 0
> < 
> * Connection #0 to host 127.0.0.1 left intact
> * Closing connection #0
> [root@localhost trafficserver]# curl -X purge -x 127.0.0.1:80 -v http://www.test.com/ben.bf
> * About to connect() to proxy 127.0.0.1 port 80 (#0)
> *   Trying 127.0.0.1... connected
> * Connected to 127.0.0.1 (127.0.0.1) port 80 (#0)
> > purge http://www.test.com/ben.bf HTTP/1.1
> > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> > Host: www.test.com
> > Accept: */*
> > Proxy-Connection: Keep-Alive
> > 
> < HTTP/1.1 200 OK
> < Date: Sat, 17 Aug 2013 06:45:29 GMT
> < Proxy-Connection: keep-alive
> < Server: ATS/3.3.5-dev
> < Content-Length: 0
> < 
> * Connection #0 to host 127.0.0.1 left intact
> * Closing connection #0
> [root@localhost trafficserver]# curl -X purge -x 127.0.0.1:80 -v http://www.test.com/ben.bf
> * About to connect() to proxy 127.0.0.1 port 80 (#0)
> *   Trying 127.0.0.1... connected
> * Connected to 127.0.0.1 (127.0.0.1) port 80 (#0)
> > purge http://www.test.com/ben.bf HTTP/1.1
> > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> > Host: www.test.com
> > Accept: */*
> > Proxy-Connection: Keep-Alive
> > 
> < HTTP/1.1 404 Not Found
> < Date: Sat, 17 Aug 2013 06:45:33 GMT
> < Proxy-Connection: keep-alive
> < Server: ATS/3.3.5-dev
> < Content-Length: 0
> < 
> * Connection #0 to host 127.0.0.1 left intact
> * Closing connection #0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira