the "net/http/httputil.DumpRequest" will destory the context value storage. about gentleman

[h2non]

With so many issues caused by wrapping context storage in http.Request.Body , I think we urgently need a solution for context storing.

Yeah, that was a design mistake, but I have plans to migrate to net/context in v2.
The good thing is that you're not restricted to use the built-in context provided in gentleman, you can now rely on net/context if you want.

[elonzh]

@h2non Yes! I am using gentleman@v2.

For now, it doesn't cause any issue in my use scene.

[elonzh]

The most important reason I using this project is the context. (The middleware and plugin system are also great features)

It will be close to perfect for me if this issue be solved.

Thanks for your work. It helped me save a lot of time, although I spent some time to debug. LOL

[h2non]

I have just pushed v2 preview release, which relies on stdlib context and gets the rid of all the previous issues with the built-in context.

Code lives in v2 branch:
https://github.com/h2non/gentleman/tree/v2

There's also an outgoing PR that would be eventually merged once the new release is more mature and I had the change to port third-party plugins/packages too: #26

You should be able to use it via:

go get gopkg.in/h2non/gentleman.v2

Let me know how it works.

[h2non]

Ping! Did you test this in gentleman@v2? If yes, please let me know how it works!

[h2non]

gentleman@v2 is finally there: https://github.com/h2non/gentleman