Jeevanandam M.

@thinkgos I think I get the point. However, I need to think about it and will take care of it in Resty v3. Maybe the name of the feature may...

@moorereason @yjhmelody Just wondering, the forever retry option is good or bad for the client library since it will result in DoS behavior on targeted application/service.

@iiiusky Typically this information gets logged in the Debug mode of Resty. Having debugged mode enabled will have some performance difference. So please test it out for your use case...

@lggomez I see your viewpoint and use case. Let's do the following - * With this PR, let's stick to current behavior, .i.e execute `responseLogger`, `parseResponseBody` middleware for all paths...

> For error paths, we don't use the error returned by it (it will break behavior and tests otherwise) @lggomez Do you mean returning an error of response middleware from...

@lggomez I'm sorry for the delay in response. I think wrapping the error will be a good choice. Please go ahead. Thanks. Also, streamlining this part in the next major...

@amarjeetanandsingh Thanks for reaching out. Ideally, you create a Resty client once in the beginning, and requests made using that client across for the purpose. Can you please share the...

@amarjeetanandsingh I'm trying to get all issues and find closure. One issue I see here is `Client.Header` exported field, having a write sync lock may not be helpful. I think...

@leewithyuan I'm sorry, I didn't get it. Do you mean throttling?

@OJFord I think you can take full control of all redirect(s) via policy. By default resty does not assign any redirect policy to the client.