Ticket #823 (enhancement)
Opened 4 months ago
Last modified 4 months ago
Automatic comparison of content-length and max_request_body_size?
Status: closed (fixed)
| Reported by: | girzel@gmail.com | Assigned to: | fumanchu |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.1 |
| Component: | wsgiserver | Keywords: | content-length, max_request_body_size |
| Cc: |
So far as I can tell, the wsgi server will not raise a 413 Request Entity Too Large until after it's begun reading the request body. There should be an early-stage comparison of the content-length request header and the max_request_body_size config setting, so that an oversized request body can be rejected out of hand.
Change History
06/23/08 23:04:29: Modified by fumanchu
- status changed from new to closed.
- resolution set to fixed.
- milestone set to 3.1.
Fixed in [1988].