Question 1

How to test HTTP API calls with Cossack in Crystal specs?

Accepted Answer

Use the built-in TestConnection to stub requests and responses, as shown in the README with examples from Glosbe and GoogleTranslate clients. This allows mocking without actual network calls for reliable unit testing.

Question 2

Does Cossack support OAuth authentication?

Accepted Answer

No, Cossack does not have built-in OAuth support; you need to implement custom middleware for OAuth flows using the modular architecture. This requires additional development effort compared to more feature-rich HTTP clients.

Question 3

Cossack or Crystal's standard HTTP::Client for simple requests?

Accepted Answer

For simple, one-off HTTP requests, use HTTP::Client as it's lighter and more straightforward. Cossack is better suited for complex clients needing middleware, testing, or cookie persistence, where its modularity adds value.

Question 4

How to implement custom logging middleware in Cossack?

Accepted Answer

Create a class inheriting from Cossack::Middleware, implement the #call method to intercept requests and responses, and use client.use to apply it. The README provides a StdoutLogMiddleware example for printing requests and responses.

Question 5

Is Cossack production-ready for Crystal applications?

Accepted Answer

Yes, it has a stable API and is used in real projects like Glosbe, but check the roadmap for missing features like basic authentication. Ensure your use case aligns with its current capabilities to avoid gaps.

Question 6

How to handle automatic HTTP redirects with Cossack?

Accepted Answer

Apply the RedirectionMiddleware with a configurable limit, as documented in the FAQ. For example, use client.use Cossack::RedirectionMiddleware, limit: 10 to follow up to 10 redirects automatically.

cossack

What is cossack?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions