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/05/04 03:52:17 UTC
[jira] [Updated] (TS-683) range_offset_limit behaviour the same as
squid
[ https://issues.apache.org/jira/browse/TS-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-683:
-----------------------------
Labels: A (was: )
> range_offset_limit behaviour the same as squid
> ----------------------------------------------
>
> Key: TS-683
> URL: https://issues.apache.org/jira/browse/TS-683
> Project: Traffic Server
> Issue Type: Improvement
> Components: HTTP
> Reporter: Kingsley Foreman
> Priority: Minor
> Labels: A
> Fix For: sometime
>
>
> Feature request, I would like to have the squid range_offset_limit behaviour added to TS,
> The "range_offset_limit" option allows a 206 connection to be made to a server, if the start range of the request is less then the ammount set in the config, eg 100k and the request is not in cache the TS server will make a 200 connection request to the backend server and treat it like a 200 download getting the entire file (while of course still sending the correct range to the client).
--
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