preview9 UseStatusCodePagesWithReExecute stopped working

[schmitch]

Currently the following code stopped working with preview9:

            app.UseStatusCodePagesWithReExecute("/Status", "?code={0}");

            app.UseRouting();

            app.UseAuthentication();
            app.UseAuthorization();

            app.UseEndpoints(endpoints =>
            {
                endpoints.MapBlazorHub();
                endpoints.MapDefaultControllerRoute();
                endpoints.MapRazorPages();
            });

I would've hoped that a authentication failure 401 would run the Status page with code=401 unfortunatly this stopped working in preview9 (preview8 worked)

[Pilchie]

@HaoK ?

[HaoK]

I'm not super familiar with status code pages, but it looks like there was a change in preview 9 here: 1f0641f#diff-a68f1924d718fb2c1219de059d8adab6

@NTaylorMullen any thoughts about whether this might affect things in this way?

[Tratcher]

We fixed UseExceptionHandlerWithReExecute but overlooked UseStatusCodePagesWithReExecute. This one also needs context.SetEndpoint(endpoint: null);

[Tratcher]

Original issue: #11233
Mitigation:

            app.UseStatusCodePagesWithReExecute("/Status", "?code={0}");

            app.Use((context, next) => {
                context.SetEndpoint(null);
                return next();
            });

            app.UseRouting();

[schmitch]

shouldn't this be attached to the 3.0.0 milestone?

[Tratcher]

It's too late for 3.0. We'll reconsider for 3.1.

[schmitch]

well isn't this a bug?! i.e. should at least be in 3.0.1?

[Tratcher]

Bugs don't automatically qualify for patching, they have to be pretty severe and hard to work around. We'll decide if a patch backport is feasible after we see what the fix looks like in 3.1.

[Tratcher]

@shirhatti @Pilchie looks like a 3.0 regression we'll need to address in 3.1.