Question 1

How to upload a file with Crest in Crystal?

Accepted Answer

Use the multipart feature by passing a File object in the form data, like `Crest.post('url', {'file' => File.open('path')})`. Crest automatically sets the Content-Type header for multipart/form-data.

Question 2

Crest vs Crystal's HTTP::Client: which should I use?

Accepted Answer

Crest is better for complex needs like authentication, streaming, and multipart uploads, offering a higher-level API. For simple GET/POST requests, Crystal's built-in HTTP::Client is lighter and sufficient.

Question 3

Does Crest support HTTP/2?

Accepted Answer

Crest is built on Crystal's HTTP::Client, which currently focuses on HTTP/1.1. HTTP/2 support would depend on the underlying library and isn't guaranteed by Crest itself.

Question 4

How to debug requests with Crest logging?

Accepted Answer

Enable logging with `logging: true` and use filters to hide sensitive data, like `request.logger.filter(/(access_token=)([^&]+)/, "\1[REMOVED]")`. This outputs formatted request details for inspection.

Question 5

Can Crest handle cookies across multiple requests?

Accepted Answer

Yes, Crest supports cookie jar persistence via `HTTP::CookieJar`, allowing cookies to be shared across requests, useful for login sessions as shown in the README examples.

Question 6

Is Crest thread-safe for concurrent use?

Accepted Answer

Crest relies on Crystal's HTTP::Client, which is generally thread-safe, but shared resources like cookie jars require careful management to avoid race conditions in concurrent environments.

Question 7

How to set up authentication with Crest?

Accepted Answer

Provide user and password parameters with `auth: 'basic'` or `'digest'` for Basic or Digest authentication. Crest automatically handles the header generation and challenge responses.

crest

What is crest?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions