"Share the Fun"

If setting CurlyOptions for every request is getting cumbersome, CurlyProvider is here to help. Global options passed to its initializer will be applied to all requests.

try services.register(CurlyProvider(globalOptions: [
    .sslCAFilePath("my-selfsigned-certs.crt")
]))

"Trust Issues"

With Curly 0.6.0, you now have fine-grained control over client and server certificate validation – no need to disable security altogether just for a self-signed certificate.

"Counting Seconds"

With Curly 0.5.0:

• The timeout and connectTimeout options lost the name of their argument. Typing out seconds: felt superfluous, especially considering...
• ...the brand new timeoutMs and connectTimeoutMs options, which allow using milliseconds for more precise control.

"Overcome Insecurities"

Curly 0.4 is here with three neat changes:

• TLS getting you down? You can now disable certificate checks with the .insecure CurlyOption. Who knows, perhaps in the future, custom certificates will be an option too.
• Speaking of the future, Swift 4.2 and 5.0 should no longer report warnings (by @mxcl).
• Speaking of reports, CURL errors are now wrapped into public CurlyErrors, so you can check what went wrong and respond accordingly (by @FredericRuaudel).

"Too Much Power"

With 0.3.0, CurlyClient got a new name: "Curly". Fancy.

But on a more serious note, 0.3.0 exposes a bunch of advanced curl options, including proxy and cookie jar support. Check the README to learn more.

"Inside // I Stand Alone"

Curly no longer requires any obscure dependencies on Linux, nor does it pull in half of the Perfect world! Using it on Heroku and Vapor Cloud should now be possible without any extra steps.