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

RequestMessage is not set on HttpResponseMessage #7

Closed
oschwald opened this issue May 6, 2015 · 2 comments
Closed

RequestMessage is not set on HttpResponseMessage #7

oschwald opened this issue May 6, 2015 · 2 comments

Comments

@oschwald
Copy link

oschwald commented May 6, 2015

In the process of testing some code, I received some confusing null reference exceptions in code paths that were known to work without the mocking. It turns out this was because mockhttp does not set the RequestMessage on HttpResponseMessage.
richardszalay pushed a commit that referenced this issue May 6, 2015
RequestMessage is now correctly assigned to responses, resolving #7
0e6bd8f
@richardszalay
Copy link
Owner

Thanks for taking the time to report this. I've fixed it and pushed out 1.2.1 to NuGet.

@oschwald
Copy link
Author

oschwald commented May 6, 2015

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@richardszalay @oschwald