You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Felix Buenemann (JIRA)" <ji...@apache.org> on 2016/04/30 20:54:12 UTC

[jira] [Comment Edited] (TS-4395) conf_purge: Simple plugin to purge an entire remap rule

    [ https://issues.apache.org/jira/browse/TS-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265426#comment-15265426 ] 

Felix Buenemann edited comment on TS-4395 at 4/30/16 6:53 PM:
--------------------------------------------------------------

Wouldn't it be better to have the secret provided via a request header?


was (Author: felixbuenemann):
Wouldn't it be better to have the secret provided via acrequest header?

> conf_purge: Simple plugin to purge an entire remap rule
> -------------------------------------------------------
>
>                 Key: TS-4395
>                 URL: https://issues.apache.org/jira/browse/TS-4395
>             Project: Traffic Server
>          Issue Type: New Feature
>          Components: Plugins
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>             Fix For: 7.0.0
>
>
> This is similar to the existing plugin to purge based on a genID stored in a persistent storage. The difference is that the purging is done exclusively via a restful API, and has little (no) overhead on performance (since the generation ID is always in memory).
> Example:
> {code}
> map http://example.com/p1  http://p1.example.com
>     @plugin=remap_purge.so @pparam=--path=__secret_purge__  @pparam=--state=example_p1
> {code}
> And to purge:
> {code}
> $ curl -s -D - -X PURGE http://example.com/p1/__secret_purge__
> HTTP/1.1 200 OK
> Date: Sat, 30 Apr 2016 00:09:34 GMT
> Connection: close
> Server: ATS/7.0.0
> Content-Length: 39
> Content-Type: text/html
> PURGED http://example.com/p1
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)