I am using Clojure Stack Lite, with authentication, which uses ring with reitit and reitit-extras for routing, and I'm seeing different behaviors between browsers that maybe someone here can help me troubleshoot.
1. In Safari, auth related routes are being blocked by the browser as 403 (Forbidden), but they work fine on Chrome.
2. Now (new behavior after a restart, no idea what change could have introduced it as all my recent changes pertain to UX only, in Chrome, any attempt to navigate to an auth URL seems to redirect to the home page without actually making a call to the web server. I've added logging, and nothing prints. However, Safari has no problem going to the login and register pages (I just can't submit a login or registration because of the 403 error). When using Safari, my new logs print as expected.
Hi, thanks for trying out the Clojure Stack lite and reporting the issue! Iβm going to reply in the github https://github.com/abogoyavlensky/clojure-stack-lite/issues/13 with a bit more context when figure out the problem. For now, I reproduced the issue in the desktop safari, and donβt have an idea yet about the reason of the issue. I suspect, it relates somehow CSRF-token and how safari send cookies. Interesting, that Safari on iOS doesnβt have this problem π€
I have no particularly clear theory about either of these issues, except the 403 error may have to do with session or csrf tokens. I was ignoring (1) for a while since Chrome was working fine, but now Chrome isn't cooperating in a completely different way, that I really don't understand.
I can try urls to pages that don't exist, and I get the expected 404 not found - the calls hit the server.
OK, duh, I figured out the problem with Chrome - I had an orphaned session and wrap-already-logged-in was redirecting to the home page. The 403 problem with Safari however remains an issue.
@abogoyavlensky isn't in this channel so I'm tagging him as the maintainer of Clojure Stack Lite. I don't know if he has a preferred channel for support issues around the stack?
@seancorfield Thanks for tagging me! Yes, the best channel for reporting such cases is Github issues, and I believe it already has been reported there (https://github.com/abogoyavlensky/clojure-stack-lite/issues/13).