Updated Harri Script from Charlie, a bunch of notes and todos for clients.
This commit is contained in:
@ -221,3 +221,11 @@ The only way to fix it it’s a requesting the user to clean cache in his browse
|
||||
to app/courses, we will redirect him to sign_in page with 301. The browser will cache sign_in page, and the user will be automatically redirected to sign_in page when the user tries visit app/courses. This will cause a loop.
|
||||
|
||||
301 makes sense if the website they are accessing was permanently moved to other location. In this case they are trying to access courses list but are redirected to sign in page because they have to be authenticated before they can access it. If we redirected them from courses to sign in page with 301 the user’s browser would save the redirect location (sign in page) and whenever the user tried to access courses web page their browser would move them automatically to sign in page making courses page inaccessible for the user. The only way out of it is cleaning browsers cache. However once they cleared the cache they would remove the cookies as well. The cookies keep the information about users identity. This is helpful because with that they don’t have to log in each time they visit our platform. But once the cookies are removed they would be again redirected to sign in page keeping them in this vicious circle. The reason to use 301 is to tell the browser “forget about this old location of the page you are accessing, this page is now here, also store this location and use it whenever you try to access this old location”.
|
||||
|
||||
|
||||
## 05/16/2023
|
||||
|
||||
Search results - can't click enough Northpass
|
||||
Only the title can be clicked when search results are returned. We need to be able to click the icon or description as well Not a problem - will get this started ASAP
|
||||
|
||||
DONE: Directly ask Chloe about the technical complications.
|
||||
|
||||
Reference in New Issue
Block a user