diff options
| author | Javier Sánchez Parra <jsanchez@soleta.eu> | 2020-04-06 11:24:19 +0200 |
|---|---|---|
| committer | OpenGnSys Support Team <soporte-og@soleta.eu> | 2020-04-06 16:35:20 +0200 |
| commit | 4d7fd58c8542c8db5309b3ba69c7bdeb2c82878b (patch) | |
| tree | e03dbb5ed9e21a451f275ba0f74672aaac838f30 /repoman/bin/opengnsys.cron | |
| parent | 1d9d93c7e9029c9ed8766002d3fc43ea7147c581 (diff) | |
#915: Reply 413 status code when no payload is too large
If the payload is too long, then the API returns a 413 status code
(following RFC 7231) instead of the resetting the communication without
replying. This way it should be more clear when this problem is
happening.
The other commit I did related to the issue of the payload size
(1d9d93c) said that ogAdmServer do not log anything when it receives a
payload of a bigger size than supported, this is false. ogAdmServer
prints the next message to the syslog when this happens:
ogAdmServer[6824]: client request from 127.0.0.1:43552 is too long
Diffstat (limited to 'repoman/bin/opengnsys.cron')
0 files changed, 0 insertions, 0 deletions