[jira] [Resolved] (TS-303) plugin idea: - a config option to transform a 'no-cache' directive into a validation 'if-modified-since' request

["Leif Hedstrom (JIRA)" <ji...@apache.org>]

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

Leif Hedstrom resolved TS-303.
------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: sometime)

This doesn't need a specific plugin, existing plugins can achieve this via configurations.
                
> plugin idea: - a config option to transform a 'no-cache' directive into a validation 'if-modified-since' request
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: TS-303
>                 URL: https://issues.apache.org/jira/browse/TS-303
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Plugins
>            Reporter: Miles Libbey
>            Priority: Minor
>
> (moved from yahoo bug 633221)
> Original description
> by John Allspaw  4 years ago at 2006-04-17 11:04
> This does disobey some of the HTTP specification, but it is a great performance
> win when you're totally sure that something hasn't/can't be changed.
> Squid has this, and this is ideally how it goes:
> "When set, this option would make TrafficServer transform a request with a
> no-cache directive into a validation (If-Modified-Since) request.  In other
> words, TrafficServer ads an "If-Modified-Since" header to the request before
> forwarding it on.  Note that this would only work for objects that have a
> Last-Modified timestamp."
> 		
>  
> Comment 1
>  by Mark Nottingham 4 years ago at 2006-04-17 13:14:30
> They other thing you could (optionally, depending on config?) do is to ignore cache-control request 
> headers all together. If you're confident of the cache's correctness, this doesn't allow the browser to force 
> a round trip back to your origin server (which could be an attack vector).
> It really doesn't break HTTP if you're acting as a gateway; they're allowed to do pretty much what they 
> want. 
> 		
>  
> Comment 2
>  by John Allspaw  4 years ago at 2006-04-17 13:20:33
> Mark: yeah, TS does already have the option to completely ignore cache-control
> headers, confirmed by Leif.  I've generally thought that having the transform
> into IMS just adds a slight amount of flexibility than the baby/bathwater if
> totally ignoring.  :)

--
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