github-actions[bot] on gh-pages
deploy: 5cf8675b97b8b92f8f727c1… (compare)
armanbilge on series
armanbilge on 0.23
Update nscplugin, sbt-scala-nat… Merge pull request #6946 from h… (compare)
http4s-steward[bot] on series
Update nscplugin, sbt-scala-nat… (compare)
Streamof requests and using its concurrency controls may be worth exploring as well.
getDefaultthrows, it just defers the explosion until the first https call. But the reason it's there is that it gives people who know that
getDefaultthrows a chance to override it. The crucial point is that
getDefaultnot appear as a default argument. That's why we've gotten that bug filed ... twice.
Some(sslContext.getDefault)is the right choice for most people.
SyncIOmakes it lazy and expresses Dragons Be Here.
F[SSLContext]could have a reasonable default.
F[SslContext], we've got a
ConcurrentEffect[F](which I'm not proud of), and then could run it in the constructor.
Http1Supportis still important though.
Http1Support, or we'd break people who can't get an
SSLContextand don't want one.