Skip to content

Make http client implementation configurable#16

Open
cen1 wants to merge 1 commit into
masterfrom
feature/configurableHttpClient
Open

Make http client implementation configurable#16
cen1 wants to merge 1 commit into
masterfrom
feature/configurableHttpClient

Conversation

@cen1

@cen1 cen1 commented Nov 29, 2020

Copy link
Copy Markdown

This partially addresses kumuluz/kumuluzee#185
The original issue can be temporarily solved by switching to http-url connector.

Jetty has default max read buffer size of 2MB which is not configurable at HttpClient level but only at Request level which is too late for us. Request is built inside jersey jetty connector so in order to support >2MB payloads a jersey patch is needed. I will try to adress the issue with upstream to move forward.
Additional problem is that http-url connector is not exposed by jersey (unlike jetty) to configure it in depth so that is the second issue I will try to adress upstream.

TODO: configure unit tests to run with http-url provider

@cen1
cen1 requested a review from urbim November 29, 2020 21:31
Comment thread README.md
rest-client:
http-client-connector: jetty # or http-url, java native http client
enable-ssl-hostname-verification: true
disable-jetty-www-auth: true

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we deprecate kumuluzee.rest-client.disable-jetty-www-auth and move it to kumuluzee.rest-client.jetty.disable-www-auth? Probably the enable-ssl-hostname-verification too.

By that I mean start using new config keys in READMEs but still support old keys as a fallback for some time.

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.

2 participants