Request log mem leak

[ryanrdoherty]

Writes all requests to temporary files, checks sizes and rejects request bodies that are too large. Then only logs body in service access log if response status code is 5xx, and even then truncates body to a reasonable level.

Possible enhancement would be to check max request size as we are writing to the file to save temp disk space and reject as soon as we go over the limit. Is it worth it?

[Foxcapades]

Possible enhancement would be to check max request size as we are writing to the file to save temp disk space and reject as soon as we go over the limit. Is it worth it?

We already have at least 2 implementations of streams that do exactly this if you wanted to port one/both of them to java:

• InputStream - Throws customizable exception when more than N bytes are read.
• OutputStream - Not the most efficient, currently throws bad request exception when attempting to write more than N bytes.