Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

HttpWebRequest in .NET Core 2.0 throwing 302 Found Exception

We are upgrading our application from .net framework to .net core 2.0.

In it, we use a HttpWebRequest to contact a site with AllowAutoRedirect set to false. When the code executed request.GetResponse() The site will return a 302 response, which in .net framework is OK - you can take response and handle it (we are after the set-cookie header value).

However, in .net core 2.0, a WebException gets thrown:

The remote server returned an error: (302) Found.

Is my understanding incorrect in that a 302 should result in an exception being thrown, rather if AllowAutoRedirect is set to false then the response should still be returned? Is there any way to trigger the same behavior experienced in .net framework?

like image 542
DenverCoder9 Avatar asked Aug 10 '17 03:08

DenverCoder9


People also ask

What causes a 302 redirect?

What is an HTTP 302? The 302 status code is a redirection message that occurs when a resource or page you're attempting to load has been temporarily moved to a different location.


2 Answers

I got the same error when setting AllowAutoRedirect to false. I solved the problem by just wrapping a try-catch-block around request.GetResponse() and assigning the Result of the exception to a variable

WebResponse response;
try {
   response = request.GetResponse();
}
catch(WebException e)) {
   if(e.Message.Contains("302")
      response = e.Result;
}
like image 155
tobias231h Avatar answered Sep 18 '22 13:09

tobias231h


Take a look at this issue - HttpWebRequest in .NET Core 2.0 throwing 301 Moved Permanently. In short, it says:

If you set AllowAutoRedirect, then you will end up not following the redirect. That means ending up with the 301 response.

HttpWebRequest (unlike HttpClient) throws exceptions for non-successful (non-200) status codes. So, getting an exception (most likely a WebException) is expected.

So, if you need to handle that redirect (which is HTTPS -> HTTP by the way), you need to trap it in try/catch block and inspect the WebException etc. That is standard use of HttpWebRequest.

That is why we recommend devs use HttpClient which has an easier use pattern.

like image 39
anatol Avatar answered Sep 16 '22 13:09

anatol