Originally created by @odenix on GitHub (Feb 14, 2024).
Moving to java.net.http.HttpClient brings many benefits, including:
HTTP/2 support
optional async mode
no need to set a system-wide default SSLSocketFactory
Instead of directly interfacing with java.net.http.HttpClient, I'd recommend to introduce a lightweight org.pkl.core.http.HttpClient facade. This keeps some flexibility and allows to enforce things like setting User-Agent.
If this sounds good, I'll work on a draft PR.
Originally created by @odenix on GitHub (Feb 14, 2024).
Moving to `java.net.http.HttpClient` brings many benefits, including:
* HTTP/2 support
* optional async mode
* no need to set a system-wide default `SSLSocketFactory`
Instead of directly interfacing with `java.net.http.HttpClient`, I'd recommend to introduce a lightweight `org.pkl.core.http.HttpClient` facade. This keeps some flexibility and allows to enforce things like setting `User-Agent`.
If this sounds good, I'll work on a draft PR.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @odenix on GitHub (Feb 14, 2024).
Moving to
java.net.http.HttpClientbrings many benefits, including:SSLSocketFactoryInstead of directly interfacing with
java.net.http.HttpClient, I'd recommend to introduce a lightweightorg.pkl.core.http.HttpClientfacade. This keeps some flexibility and allows to enforce things like settingUser-Agent.If this sounds good, I'll work on a draft PR.
@bioball commented on GitHub (Feb 14, 2024):
Hi, this sounds good! Go ahead and submit a PR for this.