Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tracing request/response is very fiddly #746

Closed
jskeet opened this issue May 12, 2016 · 5 comments
Closed

Tracing request/response is very fiddly #746

jskeet opened this issue May 12, 2016 · 5 comments
Assignees
@jskeet
Labels
Type: Enhancement

Comments

@jskeet
Copy link
Collaborator

jskeet commented May 12, 2016

When trying to work out exactly what's going wrong, it can be very useful to see the exact request and response that were sent - possibly barring compression.

Currently adding an execute interceptor allows a user to capture the request, but the response can only be captured if it causes an exception or has a failure status code... and even then it's fiddly.

We should make it easier to do this.
@jskeet jskeet self-assigned this May 12, 2016
@chrisdunelm chrisdunelm mentioned this issue Nov 14, 2016
Closed
@jskeet
Copy link
Collaborator Author

jskeet commented Mar 20, 2017

@chrisdunelm can we close this on the basis of #935?

@chrisdunelm
Copy link
Contributor

@jskeet I'd rather wait until #935 is released to nuget.

@jskeet
Copy link
Collaborator Author

jskeet commented Mar 20, 2017

Right - but then I think it'll be enough to close this. (I don't think we're waiting to do more logging-specific work.)

@chrisdunelm
Copy link
Contributor

Agreed.

@chrisdunelm
Copy link
Contributor

Released in v1.23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jskeet jskeet

Labels
Type: Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jskeet @chrisdunelm