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
if you navigate to https://seattle.codecamp.us/Home/Speakers and click on "Click here here for speaker registration." without being logged in, you will get "Sorry, an error occurred while processing your request".
The workaround is to have the user register/login first and then click this link. Instead of the error this should direct the user to a registration/login page
The text was updated successfully, but these errors were encountered:
Do you get this on the production site? I haven't been able to reproduce this but I have seen some strange behavior when debugging where if I stop my local server and go back in my session info seems to be gone but an auth cookie seems to hang around so server side I'm not logged client side it still things I'm authenticated.
Update I did see this behavior on the production site today. Question, are we updating the forms\auth timeout value when we deploy to prod? It looks like the value in the web config in source is set to two days (timeout="2880") if this is the case in prod then it could increase the odds of having a valid auth cookie with an expired server side session.
We do not deploy web.config unless there are changes to it. I make the web.config changes manually since there are bunch of sensitive info that I do not store in the repo.
If you would like to see what the prod web.config looks like, email me your MSA account so I can give you read access to the Azure account.
if you navigate to https://seattle.codecamp.us/Home/Speakers and click on "Click here here for speaker registration." without being logged in, you will get "Sorry, an error occurred while processing your request".
The workaround is to have the user register/login first and then click this link. Instead of the error this should direct the user to a registration/login page
The text was updated successfully, but these errors were encountered: