req
req copied to clipboard
imroc
Simple Go HTTP client with Black Magic
目前 `req.Request` 的 `RetryAttempt` 可以被外部读取(如：中间件中读取），但是 `retryOption` 不支持从中间件中读取，是否可以开放读取权限？ 场景：我希望在中间件中设置异常上报通知，同一个请求只有在 `RetryAttempt >= retryOption.MaxRetries` 且最终失败进行异常通知上报，避免重试过程成功，重复上报异常信息
fix https://github.com/imroc/req/issues/471
使用中发现，如果服务端校验http header Accept的情况会导致请求异常，这里是否考虑增加application/json ``` chromeHeaders = map[string]string{ "pragma": "no-cache", "cache-control": "no-cache", "sec-ch-ua": `"Not_A Brand";v="8", "Chromium";v="120", "Google Chrome";v="120"`, "sec-ch-ua-mobile": "?0", "sec-ch-ua-platform": `"macOS"`, "upgrade-insecure-requests": "1", "user-agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X...
GET https://www.baidu.com/ HTTP/1.1 Accept-Encoding: gzip Content-Length: 0 Host: www.baidu.com User-Agent: 123 当前使用 req.C() 创建请求后 会默认补充Accept-Encoding User-Agent 是否可以禁止掉完全由用户自主设置
For status code (500) - resp.Err was nil resp.Status was 500 INTERNAL SERVER ERROR `Do(...).Into()` was failing to unmarshal
```go // EnableForceHTTP1 enable force using HTTP1 (disabled by default). // // Attention: This method should not be called when ImpersonateXXX, SetTLSFingerPrint or // SetTLSHandshake and other methods that will...
I believe there's a race between the two paths when using HTTP/3 for the transport. I found this when hitting a `panic` here in `internal/http3/transport.go`: ``` return conn, t.newClientConn(conn), nil...
