From: Zoran V. <zv...@ar...> - 2005-06-16 20:58:10
|
Am 16.06.2005 um 22:13 schrieb Stephen Deasey: > > At any time before the registered proc asks for the content it can > check the content length header and decide whether it is too large to > accept. You could imagine setting a low global maxinput, and a call > such as Ns_ConnSetMaxInput() which a registered proc could call to > increase the limit for that connection only. The advantage over the > limits scheme in 4.1 is that the code which checks the size of the > content and processes it is kept together, rather than having to > pre-decalare maxinput sizes for arbitrary URLs in the config file. > Aha... do: ns_conn setmaxinput before we do ns_conn content to get the content of the request. Hm... so we'd keep the maxinput reasonably *small* for most of the requests and will re-set it to a larger value *before* requesting the content when we anticipate large file upload. I think I'm beginning to understand.... Yes, this makes sense. Zoran |