F
Filamentβ€’3mo ago
jjo63

Application load failure on Safari but OK on Chrome

Hi all, bit of an odd one this. I developed originally using the php server and all was good. I then wanted to make the app accessible to a wider audience for evaluation and so I configured apache and setup SSL etc. The issue occurs on logging in: If I login to the app on Safari using the php server (port 8000) all OK. If I login to the app on Safari using apache (443) I get an error. If I login to the app on Chrome using apache (443) all OK. The error is
The POST method is not supported for route admin/login. Supported methods: GET, HEAD.
Any thoughts or experience of this? thanks j
Solution:
OK. Interesting! Worked in private mode.
Jump to solution
9 Replies
toeknee
toekneeβ€’3mo ago
get/head isn't for login at all....
jjo63
jjo63OPβ€’3mo ago
Here is a link to the Flare https://flareapp.io/share/xmNee0Q5
Flare
The POST method is not supported for route admin/login. Supported methods: GET, HEAD. - The error occurred at https://hcat.hopto.org/admin/login
jjo63
jjo63OPβ€’3mo ago
Also - on the loging page, the password fields are not protected with * - the password is always clearly visible as you type in Safari - again, this is different in Chrome (where it behaves as expected).
toeknee
toekneeβ€’3mo ago
Have you customised the login page?
jjo63
jjo63OPβ€’3mo ago
No (sorry for the curt reply πŸ™‚ )
toeknee
toekneeβ€’3mo ago
Not really making any sense, the error you are getting shouldn't be browser specific. Can you try again in private mode?
Solution
jjo63
jjo63β€’3mo ago
OK. Interesting! Worked in private mode.
toeknee
toekneeβ€’3mo ago
Sounds like you could have an extension interferring
jjo63
jjo63OPβ€’3mo ago
Hmmm - well that's a complete mystery - i only had a few extensions - parallels desktop-related + "coupert" - I deleted all but one of these, restarted Safari and now it's behaving as expected. Bit of a nuisance as it's possible that other users in the future might hit this rather unusual combination and it'd be alarming for them to (a) see their password in clear text and (b) then get the error that I reported. I'm glad to see that it's resolved for me, here, but would be great to be able to look more deeply into what the problem is (as no other applications to my knowledge seem to be affected by the presence of browser extensions).
Want results from more Discord servers?
Add your server