The max_response_size limit is not working. Why? Fix!

Description

Based on the BES context max_response_size being set to 100 (kilobytes) this request should be rejected:

But it is not. Why? Can we fix it?

Environment

None

Activity

Show:
Nathan Potter
March 20, 2019, 10:53 AM

I think it's important to test this with the OLFS too, as it seems there is some kind of messed up state persistence happening that may be part of the mysterious behavior where the OLFS issues the command over an existing connection and max_response_size is ignored, but when new connections are made using bescmdln and besstandalone the same command works as expected.

Done
Your pinned fields
Click on the next to a field label to start pinning.

Assignee

James Gallagher

Reporter

Nathan Potter

Labels

Fix versions

Time remaining

0m