[ 
https://issues.apache.org/jira/browse/TS-4772?focusedWorklogId=26953&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26953
 ]

ASF GitHub Bot logged work on TS-4772:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Aug/16 18:55
            Start Date: 23/Aug/16 18:55
    Worklog Time Spent: 10m 
      Work Description: Github user zwoop commented on the issue:

    https://github.com/apache/trafficserver/pull/897
  
    I guess I don't have a strong opinion, but it seems unfortunate to me to 
introduce these new options as headers, rather than URI components. The 
original plugin for lighthttpd did everything in the URI paths, no? Keeping it 
this way seems more consistent, and easier to use for e.g. setting up various 
performance and load patters where you want to mix various options for various 
requests.
    
    In a sense, it'd cool to mimic some of the behavior of httpbin.


Issue Time Tracking
-------------------

    Worklog Id:     (was: 26953)
    Time Spent: 1h  (was: 50m)

> Add delay and max-age control to the generator plugin.
> ------------------------------------------------------
>
>                 Key: TS-4772
>                 URL: https://issues.apache.org/jira/browse/TS-4772
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Plugins
>            Reporter: James Peach
>            Assignee: James Peach
>             Fix For: 7.0.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Add configurable control over the response delay and the {{max-age}} in the 
> cached response. This makes it easier to test cache revalidation scenarios.



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

Reply via email to