setting range_offset_limit per domain

The other day I posted a question on squid-users asking if it was
possible to specify range_offset_limit per domain. Henrik advised me
that this is not currently possible, but that it shouldn't be hard to
implement. I'm interested in attempting to implement this myself, and I
just wondered if someone could tell me how to get started with the
development process.

Also, I wonder if anyone has any input on how this should be achieved
configuration-wise. I thought about making it backwards compatible by
changing the directive to:

range_offset_limit (bytes) [pattern]

Where pattern is a regex that the url from the request would be matched
against. This would actually not only give us the ability to implement
it per domain, but we would even have fine grained control per specific
url. Then we could have multiple range_offset_limit lines that would be
parsed in order, using the first line that matched the url in a
request. Then, we could have an implied last line that is
"range_offset_limit 0 *" that would catch everything else.

That was just the first thing that popped into my head, and I haven't
started reading the code yet. I just wanted to know where to start and
get people's opinions.
Received on Mon Oct 05 2009 - 20:51:43 MDT