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.
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
Making a web request with CachePolicy and Fiddler on causes null-reference exception #24363
Comments
Does it happen on .NET Core as well? |
No idea. I don't think that API is in .NET Core. @terrajobst asked me to log it here. |
Just to confirm... I don't see the members that the stack trace points to in CoreFX: https://github.com/dotnet/corefx/blob/e3f74deb999571d3f34a6b2b8011caebcf06dbfc/src/System.Net.Requests/src/System/Net/HttpWebRequest.cs |
cc: @terrajobst .NET Framework bugs should NOT be reported to this repo. Instead, they should be reported on developercommunity.visualstudio.com. Here is an example bug that was originally opened in GitHub but moved: We suggest customers use the developercommunity.visualstudio.com portal to report issues with .NET Framework. Doing so will allow the right product group people to get involved, get an internal .NET Framework bug generated, and provide a channel for posting repro code and/or additional information back to the product team as well as report back status to the person opening the bug. |
We have moved the bug here so that it will be logged as a bug in .NET Framework. You will be able to track status from there. |
FYI:
|
@karelz Thanks for the update. That's great news. |
This bug occurs in .NET FX (tested .NET Framework 4.5.2 and 4.7). It only occurs when Fiddler is running as well.
The reproducer is a simple GET request with the cache policy enabled:
This request will fail with a
HttpRequestException
, but if you look at the inner exceptions, what's really happening is aNullReferenceException
inHttpWebRequest.CheckCacheUpdateOnResponse():
https://github.com/Microsoft/referencesource/blob/7de0d30c7c5ef56ab60fee41fcdb50005d24979a/System/net/System/Net/HttpWebRequest.cs#L4310
It doesn't seem to happen with all URLs. The above URL has an attachment in the response, which I suspect is related.
/CC @Fragmer
The text was updated successfully, but these errors were encountered: