DefaultHttpResponse does not account for other redirect status codes

[smarts]

Status codes 303, 307, & 308 are valid redirect codes and should be incorporated into DefaultHttpResponse. My guess is that 303 probably isn't a big deal, but the other 2 should definitely be handled.

[Tratcher]

You mean the public override void Redirect(string location, bool permanent) API?
https://github.com/aspnet/HttpAbstractions/blob/dev/src/Microsoft.AspNetCore.Http/Internal/DefaultHttpResponse.cs#L125

Is this theoretical or do you really want to send 307/308 in your app?

[smarts]

Yup, that's the API. And no, it's not theoretical.

[smarts]

What do you think about adding bool preserveMethod as an optional parameter to the Redirect() method (defaulted to false)?

[muratg]

Putting this in Discussions now. Let's see if we get more feedback on these newer status codes.

In the meantime, @smarts, you could write your own extension methods to get this functionality.

[smarts]

True @muratg, but what I can't do is change the existing RedirectToRouteResult to add a PreserveMethod property so that I can take advantage of this in the built-in RedirectToRoute() and RedirectToRoutePermanent() controller methods.

[Tratcher]

So even if we added this here you'd also want changes to MVC.

[smarts]

Yes, @Tratcher. The RedirectToRouteResult (and the other redirect result classes) would presumably need to add a PreserveMethod property so that RedirectToRouteResultExecutor can propagate it down to the HttpResponse.Redirect() call.

[Tratcher]

Please file another bug on MVC. That can be implemented independent of this one.

[muratg]

We are closing this issue because no further action is planned for this issue. If you still have any issues or questions, please log a new issue with any additional details that you have.