Some suggestions for clarifying client_max_body_size

Hello. After installing a “fresh” 1.4.4 nginx with passenger the other
day, I had a few suggestions/feature requests for the default install:

by default the client_max_body_size can easily be exceeded. I think
this takes many people by surprise (at least it did for me) when small
uploads work but larger ones don’t…

A couple of possible feature requests/suggestions, thus:

by default in nginx.conf list it, with its default (and possibly even an
explanation that this is the max POST upload size).

Maybe in the error log it could mention the config param, etc. like

*216 client intended to send too large body: 15004020 bytes >
client_max_body_size 1000000, client: …

(currently it says this)

2013/12/09 14:35:26 [error] 26537#0: *216 client intended to send too
large body: 15004020 bytes, client: …

Anyway something like that (or possibly even return a 413 instead of
dropping the connection, as long as it has free connections available at
all?) That one might not be viable, just debating it.

Anyway just throwing out some ideas there.
Thank you for an excellent product.

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