Client_max_body_size bug or documentation issue again?

Hi,
When testing out the client_max_body_size directive on the wiki and
in the original russian docs it says it can be used in http, server,
or location. But in testing it seems that it only works in http or
server and location is ignored. I did some basic tests with config
file moving the directive around and never got it to work inside a
location block. this was original noticed at
http://forum.slicehost.com/comments.php?
DiscussionID=1714&page=1#Item_13 the person there was using nginx
0.5.x while i tested it on 0.6.29 (not 30 as it was just released) and
still had this issue.

V/r,
Rob S.

On Tue, Apr 29, 2008 at 08:48:15PM -0500, Rob S. wrote:

When testing out the client_max_body_size directive on the wiki and
in the original russian docs it says it can be used in http, server,
or location. But in testing it seems that it only works in http or
server and location is ignored. I did some basic tests with config
file moving the directive around and never got it to work inside a
location block. this was original noticed at
http://forum.slicehost.com/comments.php?
DiscussionID=1714&page=1#Item_13 the person there was using nginx
0.5.x while i tested it on 0.6.29 (not 30 as it was just released) and
still had this issue.

The client_max_body_size directive should work inside location.
I could not reproduce the bug. Could you create debug log of your case ?

Sorry i went back to look at my configuration for testing. I found out
my location block wasn’t being triggered at all anyways because i was
passing off to php fastcgi process to do the processing of the upload
(Since i found out you cannot post to static files for testing) so it
was using the php location block instead. So i redid all my testing
and used a proxy_pass on location / block and from there i was not
able to reproduce it. Sorry for wasting mail traffic on this bogus mail.

v/r
Rob S.