Hello,
Looking for a way to limit the size of any files served by Apache. There is a setting for limiting the size of a request, but couldn't find any that disallows serving files that are larger than some size.
Is there a way to take care of this directly? Or maybe indirectly, through a module that can check every file served and take rule-based actions ...
Sameer.
On 23/06/04 11:43 +0530, Sameer D. Sahasrabuddhe wrote:
Hello,
Looking for a way to limit the size of any files served by Apache. There is a setting for limiting the size of a request, but couldn't find any that disallows serving files that are larger than some size.
mod_throttle may be useful. What exactly are you trying to achieve?
Devdas Bhagat
On Thu, Jun 24, 2004 at 10:21:20PM +0530, Devdas Bhagat wrote:
Looking for a way to limit the size of any files served by Apache. There is a setting for limiting the size of a request, but couldn't find any that disallows serving files that are larger than some size.
mod_throttle may be useful. What exactly are you trying to achieve?
Will try that out. Trying to achieve exactly what I said ... not allowing users to put unreasonably large files for download on their websites.
Sameer.
Will try that out. Trying to achieve exactly what I said ... not allowing users to put unreasonably large files for download on their websites.
why can't you run a script to do that file-size checking on the server ?? whenever an addition is made to any user directory u might do exactly that. then again u could put up userquotas ? or another option being running a script to parse the webpages of the users and remove the links to such heavy files.
just my 2ps of course, C
On Fri, Jun 25, 2004 at 08:25:18PM +0530, Chetan S wrote:
why can't you run a script to do that file-size checking on the server ?? whenever an addition is made to any user directory u might do exactly that. then again u could put up userquotas ? or another option being running a script to parse the webpages of the users and remove the links to such heavy files.
Yeah we thought of those ideas ... but it's too much trouble, especially in terms of policy. I am talking about department servers, where people are given lots of freedom and expected to use resources thoughtfully. I dread to think of touching anyone's home directory, it's better if there's a way to impose hard limits on what gets served, rather than what users do with their own data.
Amitay had suggested that I could use squid's capabilities in this regard. I suppose the idea would be to run apache on a different port, and relay everything through squid on port 80 ... would that be too much of an overhead for this task?
Sameer.
-
Chetan S -
Devdas Bhagat -
Sameer D. Sahasrabuddhe