Faysal Banna created TS-2643:
--------------------------------
Summary: Origin Server Throttling
Key: TS-2643
URL: https://issues.apache.org/jira/browse/TS-2643
Project: Traffic Server
Issue Type: New Feature
Components: Network, Plugins
Reporter: Faysal Banna
Hi Guys
wonder if its too much work to request for implementing a feature to rate
limiting (throttling) bandwidth (bytes/sec) for data from Origin Servers , yet
i know not where would it be implemented, and since we take most of the headers
requested and responses in the header_rewrite and we can apply/override rules
per txn in header_rewrite, The idea is that since we do time condition and set
background filling and chance some stuff in the header_rewrite
why cann't we issue a configurable request to records.config to limit this txn.
its for the reason needed so that at some peak hours clients who are using
downloads or watching some porn movies would be rate limited at those times,
and maybe for example windows updates that work in background would not consume
much of my bandwidth from origin server
and leave space more for the interactive pages and stuff to pass through
thats why i said if it possible to do it in header_rewrite plugin cause as far
its the only plugin i seen that can override configurable rules as per
request
am not sure how the internals of the ATS works per transaction. thats why my
thought was in header_rewrite. yet i guess it might land in some new plugin
throttle_plugin or so. taking into consideration that it needs to inspect the
requested headers and the time it is requested at.
much regards
Faysal Banna
--
This message was sent by Atlassian JIRA
(v6.2#6252)
