Preserving Querystring w/ UseStatusCodePagesWithReExecute

[tysonnero]

Is it possible to preserve the original querystring when using UseStatusCodePagesWithReExecute. If so, will the params stay on the url or will they be stored somewhere else? If stored somewhere else :-), how are they accessed after the fact?

Thanks!

[Tratcher]

Yes, see

Diagnostics/src/Microsoft.AspNetCore.Diagnostics/StatusCodePage/StatusCodePagesExtensions.cs

Lines 185 to 190 in 3a868d8

	context.HttpContext.Features.Set<IStatusCodeReExecuteFeature>(new StatusCodeReExecuteFeature()
	{
	OriginalPathBase = context.HttpContext.Request.PathBase.Value,
	OriginalPath = originalPath.Value,
	OriginalQueryString = originalQueryString.HasValue ? originalQueryString.Value : null,
	});

[tysonnero]

@Tratcher Thanks for the quick response.

Do I have to upgrade to AspNetCore 1.1 for this? I am currently on 1.0.
And, how do you get at that OriginalQueryString from a Controller or View?

[Tratcher]

No, that's in 1.0. https://github.com/aspnet/Diagnostics/blob/1.0.0/src/Microsoft.AspNetCore.Diagnostics/StatusCodePage/StatusCodePagesExtensions.cs#L188
In an MVC controller you can call HttpContext.Features.Get<IStatusCodeReExecuteFeature>()

[tysonnero]

I can't seem to get at OriginalQueryString b/c it's not in the IStatusCodeReExecuteFeature interface. I'm getting compile time errors.

[Tratcher]

Ah, you found a bug. The original commit (48b436e) added OriginalQueryString to StatusCodeReExecuteFeature but not to the interface IStatusCodeReExecuteFeature. You can work around this by downcasting to StatusCodeReExecuteFeature.

@muratg, as this requires a change to the interface we'll have to wait until 2.0.