Bug: HttpProxyModule doesn't report errors using proxy_temp

If HttpProxyModule can’t write to the directories inside proxy_temp
(eg they are owned by root not server uid) then requests for URLs of
large size fail after 102400 bytes, they hang in the client, then
timeout and no errors are printed.
In fact access_log shows code 200 for each request which was quite
puzzling to debug.
maybe nginx -t should alert if one of the _temp directories has
unwritable files or directories in it?
thanks.

Hello!

On Sat, Oct 16, 2010 at 10:15:36AM +1100, jb wrote:

If HttpProxyModule can’t write to the directories inside proxy_temp
(eg they are owned by root not server uid) then requests for URLs of
large size fail after 102400 bytes, they hang in the client, then
timeout and no errors are printed.

On error writing to proxy temp nginx logs “[crit] … open() …
failed …” message to error log and closes connection.

In fact access_log shows code 200 for each request which was quite
puzzling to debug.

Status code is one sent to client. It’s good idea to look into
error log when you are trying to debug errors.

Actually, it’s good idea to look into error log even if you are
not trying to debug errors.

maybe nginx -t should alert if one of the _temp directories has
unwritable files or directories in it?

Temp directories may contain lots of subdirectories and
scanning them all isn’t considered wise.

Maxim D.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs