@Hackysack@_benjaminpetit@_MihaZupan Try removing the route attribute from the account controller. I think it's using the wrong pattern, overriding the default, and making the action unrouteable. That would explain why you keep ending up in the catch-all route.
@cecilphillip@CordasFilip Not done yet. Mostly it's missing a committed partner to help verify requirements and implementation. There is a sample in the repo.
Heads up .NET Twitter, I'm jumping to a new team soon outside of AspNetCore/.NET. I'll still be an AspNetCore customer and contributor. I've got to go YARP all the things.
@DamianEdwards@jhigh2000@davidfowl@halter73 H/2 is much more complicated, but we should still be able to suspend timeouts. Do the trace level server logs what happened?
File an issue on GitHub please.
@ladeak87 @davidfowl Oh, the AOT work can likely trim out SslStream so TLS won't work for Http 1 or 2, but 3 could still work because it uses a different TLS code path.
@kahbazi@MicrosoftLife@davidfowl@DamianEdwards Fowler won't let us put the wheels on until the motor is ready to go 120mph. Damian will drive 120mph. I'll be re-enforcing my seatbelt and installing extra grips.
Improving the authentication and authorization experience in #aspnetcore apps is something our team has been focused on from the release of #dotnet 7. This blog post details our plans for ASP .NET Core 8 and includes a survey link for your feedback.
https://t.co/fTNQ2N3nzf