Question 1

How do I set custom timeouts with mozillazg/request?

Accepted Answer

Configure timeouts on the underlying http.Client instance before passing it to request.NewRequest(). For example, set client.Timeout to control deadlines, as the library doesn't provide its own timeout settings.

Question 2

Is mozillazg/request better than using Go's net/http directly?

Accepted Answer

It offers a simpler API for common tasks, reducing boilerplate, but net/http provides more control and is standard. For complex or performance-critical apps, net/http might be preferable.

Question 3

How to handle retries and error recovery with this library?

Accepted Answer

You need to implement custom retry logic, as the library doesn't include built-in retry mechanisms. Error handling is similar to net/http, requiring manual checks after each request.

Question 4

Does mozillazg/request support OAuth or JWT authentication?

Accepted Answer

It only supports basic authentication via req.BasicAuth. For OAuth or JWT, you must set custom headers manually, as there are no dedicated helpers.

Question 5

How to parse XML or HTML responses instead of JSON?

Accepted Answer

Use resp.Json() for JSON parsing, but for other formats, read resp.Body directly and use appropriate parsers, just as you would with standard net/http.

Question 6

Is mozillazg/request still actively maintained?

Accepted Answer

The README shows CI badges and documentation, but check the GitHub repository for recent commits, as it might be stable but not frequently updated compared to newer libraries.

request

What is request?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions