Skip to content

Conversation

@cen1
Copy link
Contributor

@cen1 cen1 commented Jan 8, 2021

Adds a new jetty specific client property to set the max response buffer size. If property is not set, the old code path is used and exception is thrown for large responses (bigger than 2MiB).

This addresses the immediate paint point and is least invasive. Exception is still thrown if response size is too big even for the custom size. Since this behaviour differs from async path it might be a good idea to just
replace it completely in some major release.

@cen1
Copy link
Contributor Author

cen1 commented Jan 8, 2021

Fixes #4646

…fer size. If property is not set, the old code path is used and exception is thrown for large responses (bigger than 2MiB).

This addresses the immediate paint point and is least invasive. Exception is still thrown if response size is too big even for the custom size. Since this behaviour differs from async path it might be a good idea to just
replace it completely in some major release.

Signed-off-by: Klemen Ferjancic <cen.is.imba@gmail.com>
@cen1 cen1 force-pushed the feature/jettyConfReadBuffer branch from 7acfdca to dfd5080 Compare January 8, 2021 19:41
@jansupol
Copy link
Contributor

I like the PR. Would you mind updating the copyright year to 2021 in the modified files?

Signed-off-by: Klemen Ferjancic <cen.is.imba@gmail.com>
@senivam senivam linked an issue Jan 14, 2021 that may be closed by this pull request
@jansupol jansupol merged commit 500c0d7 into eclipse-ee4j:master Jan 14, 2021
@senivam senivam added this to the 2.34 milestone Jan 15, 2021
@cen1 cen1 deleted the feature/jettyConfReadBuffer branch February 12, 2021 07:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Jetty connector client response buffer is hard limited to 2MB

3 participants