maxRequestSize flag has no effect #127
Merged
+1
−2
Conversation
… FinatraServer object is loaded and hence uses only the default value of 5MB - fix is to make codec lazy val
|
good catch! thanks! |
twoism
added a commit
that referenced
this pull request
Mar 24, 2014
maxRequestSize flag has no effect
cacoco
pushed a commit
that referenced
this pull request
May 13, 2015
maxRequestSize flag has no effect
cacoco
pushed a commit
that referenced
this pull request
May 14, 2015
maxRequestSize flag has no effect
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
maxRequestSize flag has no effect because codec gets initialized when FinatraServer object is loaded and hence uses only the default value of 5MB - fix is to make codec lazy val