BlazeClientBuilder: SslContext.getDefault can throw outside the monad
See original GitHub issueThis is another appearance of the problem mentioned in #1956 . On some systems SslContext.getDefault
can throw, which is not handled correctly. BlazeClientBuilder
uses SslContext.getDefault
as a default argument, which leaves capturing the exception to the user.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
http4s/http4s - Gitter
Hi All! I just asked this in FS2, but maybe here is better. Can I use http4s to connect to a remote websocket,...
Read more >SSLContext (Java Platform SE 8 ) - Oracle Help Center
This protocol is described in the SSLContext section of the Java Cryptography ... public static SSLContext getDefault() throws NoSuchAlgorithmException.
Read more >Changelog - http4s
A server we connect to with http4s-async-http-client could theoretically respond with a large or malicious compressed stream and exhaust memory in the client ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Maybe in the long run, a sum type rather than abusing
Option
is a better way to express this. But #2604 fixes this in a binary compatible way in 0.20.Hi @nigredo-tori - I’m sorry that I was not clear. My above question was meant for the http4s maintainers.