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
{{ message }}
This repository has been archived by the owner on Mar 8, 2021. It is now read-only.
It appears that when a linked file (such as favicon.ico) is requested resulting in a 404, friend uses that resource as the last uri to redirect to after authetication. I ran into this problem on Chrome without fail, but after the first 404 Firefox ignored it.
The text was updated successfully, but these errors were encountered:
I ran in the same scenario. What I did was just creating a route for favicon (GET "/favicon.ico" [] (resp/redirect "/")) and now it correctly redirects to / but that's not a good solution. There should be a way to tell friend which route to redirect to after login.
It appears that when a linked file (such as favicon.ico) is requested resulting in a 404, friend uses that resource as the last uri to redirect to after authetication. I ran into this problem on Chrome without fail, but after the first 404 Firefox ignored it.
The text was updated successfully, but these errors were encountered: