mirror of
https://github.com/EDCD/EDDN.git
synced 2025-06-11 04:42:28 +03:00
schemas/README: bottle body size limit *is* affected by compression
I explicitly tested this with a 50KiB limit on beta EDDN service: 1. 49973 byte message does make it through, in plain text. 2. 51312 byte message, no compression, 413. 3. Same message, with gzip compression, 200 4. The 149242 byte file I based those extra ones on also makes it through when compressed. Indeed the Gateway logging cites the compressed-body size. `bottle` isn't looking at the message and magically decompressing it in order to check plain-text size.
This commit is contained in:
parent
853c309df0
commit
a8f657c2d6
@ -332,8 +332,10 @@ make a valid request" responses you might experience the following:
|
|||||||
|
|
||||||
#### bottle responses
|
#### bottle responses
|
||||||
1. `413` - `Payload Too Large` - `bottle` enforces a maximum request size
|
1. `413` - `Payload Too Large` - `bottle` enforces a maximum request size
|
||||||
and the request exceeds that. As of 2022-01-07 the limit is 1MiB, and
|
and the request exceeds that. As of 2022-01-07 the limit is 1MiB,
|
||||||
pertains to the plain-text size, not after gzip compression if used.
|
which is versus the compressed size of the body, if compression is
|
||||||
|
used. Thus compression *will* allow for sending approximately 10x
|
||||||
|
larger messages.
|
||||||
To verify the current limit check for the line that looks like:
|
To verify the current limit check for the line that looks like:
|
||||||
|
|
||||||
```
|
```
|
||||||
|
Loading…
x
Reference in New Issue
Block a user