You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a middleware that calls onceBasic() to add password protection to a route. Prior to upgrading to 5.5 when I hit the route it would cause the browser to display the username/password dialog for HTTP Basic authentication. Now after upgrading to 5.5 I get a Symfony\Component\HttpKernel\Exception\UnauthorizedHttpException and the Symfony exception handler renders an error page showing the exception. I believe this is related to this commit 37fb414 it is throwing an exception instead of a response and it looks like the exception is rendered by the exception handler instead of sending a 401 with the WWW-Authenticate: Basic header.
Steps To Reproduce:
The text was updated successfully, but these errors were encountered:
@ejunker Though I'm pretty sure this will be fixed at the framework level soon, you can fix this in your app by catching UnauthorizedHttpException in the exception handler. Here's an example from my app.
Description:
I have a middleware that calls
onceBasic()
to add password protection to a route. Prior to upgrading to 5.5 when I hit the route it would cause the browser to display the username/password dialog for HTTP Basic authentication. Now after upgrading to 5.5 I get aSymfony\Component\HttpKernel\Exception\UnauthorizedHttpException
and the Symfony exception handler renders an error page showing the exception. I believe this is related to this commit 37fb414 it is throwing an exception instead of a response and it looks like the exception is rendered by the exception handler instead of sending a 401 with theWWW-Authenticate: Basic
header.Steps To Reproduce:
The text was updated successfully, but these errors were encountered: