Question 1

How do I handle OAuth2 token refresh with Resty?

Accepted Answer

Use Resty's request/response middleware hooks to intercept responses and refresh tokens when needed. Set up an OnAfterResponse hook to check for authentication errors and update tokens dynamically, as shown in the documentation examples.

Question 2

Resty vs Go's net/http: which is better for simple API calls?

Accepted Answer

For simple, one-off requests, net/http might suffice with less overhead. Resty shines when you need features like retries, auth, or debugging—it abstracts common pain points but adds a dependency. Choose based on your project's complexity.

Question 3

Does Resty support HTTP/2 fully?

Accepted Answer

Resty builds on Go's net/http, which supports HTTP/2, but Resty's abstraction may not expose all advanced HTTP/2 features like server push directly. Check the docs for specific configurations, as you might need to tweak the underlying transport.

Question 4

How to upload multiple files with Resty?

Accepted Answer

Use the SetMultipartFields method to attach multiple files in a single request. Resty handles the multipart encoding automatically, allowing you to specify file paths or readers with minimal code.

Question 5

What's the performance impact of using Resty middleware?

Accepted Answer

Middleware hooks add some latency per request, but for most applications, the convenience outweighs the cost. In high-throughput scenarios, benchmark to ensure the overhead is acceptable, as direct net/http calls are faster.

Question 6

Can I use Resty for consuming real-time Server-Sent Events?

Accepted Answer

Yes, Resty has native SSE support. Use methods like SetDoNotParseResponse and stream events with OnResponse middleware or dedicated SSE functions, enabling efficient handling of event streams without extra libraries.

resty

What is resty?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions