summaryrefslogtreecommitdiffstats
path: root/tests/units/test_0016_post_image_create.py
diff options
context:
space:
mode:
authorJavier Sánchez Parra <jsanchez@soleta.eu>2020-04-06 11:24:19 +0200
committerOpenGnSys Support Team <soporte-og@soleta.eu>2020-04-06 16:35:20 +0200
commit54d172e972067e4ddcfd11c613929af811754f99 (patch)
tree3bc373874c80453e8ec49770a2d4e23d078cbd26 /tests/units/test_0016_post_image_create.py
parent286dcd72eb88b8d5e25a386b71d120d5ce534fbb (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 'tests/units/test_0016_post_image_create.py')
0 files changed, 0 insertions, 0 deletions