On Sat, 25 Oct 2003 11:11:31 +0200 (CEST) Henrik Nordstrom <[EMAIL PROTECTED]> wrote:
> He then need to wait > as much time for the quota to refill until he has access to the Internet > again. there is another unbeatable situation (typical for internet cafes and clubs) - one time generated and used logins. > > Maybe this could be solved by sending HEAD request in the self written > > redirector program and compare "Content-lenght:" field if present with > > current user quota. i don't know. > > No, this is not a good approach for technical reasons, but it can be > solved by adding native quota support to Squid. is there some plans in the development team about it? > However, personally I would prefer the relaxed approach where users are > allowed to temporarily go above quota. If not users will not ever be able > to download very large objects as they will always be above their quota. > With the relaxed approach they will be able to download this large object, > but then won't be able to access the Internet for a longer time > compensating for the fact that they overused their quota. again, think of one time used user logins. > What is important in both is that the user when denied access due to quota > gets a clear message indicating what is the problem and when he will get > access again, and optionally a link to where to purchase/negotiate > additional bandwidth. this is where "deny_info" comes into play. we use it. olegs
