> it should not be necessary to clear all cookies because this has wider implications There is another workaround: * Press ctrl+h (or alternatively go to the hamburger menu at the top right, select history, then Manage History at the bottom) * search for `keep.education` * right click on a history entry * click on "Forget about this site" > Besides, we don't want to have to ask our clients to clear their cookies either every time they end up with a page FYI: The problem is, that the website told the browser on a previous visit that there is a (permanent) redirect to another URL. If you have never visited Firefox when that redirect was in place (for example if your clients didn't visit the website at that time), then they just load the current website from the webserver as expected. AFAIK Chrome has the same behavior: If you would have visited the website before with chrome, you would see the misleading redirect behavior. We're planning to take a look at the caching behavior in Bug 968273, to make redirects received over the insecure http (as opposed to https) not permanently cached. That will help with situations like this.
Bug 1869588 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> it should not be necessary to clear all cookies because this has wider implications There is another workaround: * Press ctrl+h (or alternatively go to the hamburger menu at the top right, select history, then Manage History at the bottom) * search for `keep.education` * right click on a history entry * click on "Forget about this site" > Besides, we don't want to have to ask our clients to clear their cookies either every time they end up with a page FYI: The problem is, that the website told the browser on a previous visit that there is a (permanent) redirect to another URL. If you have never visited the website with Firefox when that redirect was in place (for example if your clients didn't visit the website at that time), then they just load the current website from the webserver as expected. AFAIK Chrome has the same behavior: If you would have visited the website before with chrome, you would see the misleading redirect behavior. We're planning to take a look at the caching behavior in Bug 968273, to make redirects received over the insecure http (as opposed to https) not permanently cached. That will help with situations like this.
> it should not be necessary to clear all cookies because this has wider implications There is another workaround: * Press ctrl+h (or alternatively go to the hamburger menu at the top right, select history, then Manage History at the bottom) * search for `keep.education` * right click on a history entry * click on "Forget about this site" > Besides, we don't want to have to ask our clients to clear their cookies either every time they end up with a page FYI: The problem is, that the website told the browser on a previous visit that there is a (permanent) redirect to another URL. If you have never visited the website with Firefox when that redirect was in place (for example if your clients didn't visit the website at that time), then they just load the current website from the webserver as expected. AFAIK Chrome has the same behavior: If you would have visited the website before with Chrome, you would also see the misleading cached redirect behavior. We're planning to take a look at the caching behavior in Bug 968273, to make redirects received over the insecure http (as opposed to https) not permanently cached. That will help with situations like this.
> it should not be necessary to clear all cookies because this has wider implications There is another workaround: * Press ctrl+h (or alternatively go to the hamburger menu at the top right, select history, then Manage History at the bottom) * search for `keep.education` * right click on a history entry * click on "Forget about this site" > Besides, we don't want to have to ask our clients to clear their cookies either every time they end up with a page FYI: The problem is, that the website told the browser on a previous visit that there is a (permanent) redirect to another URL. If you have never visited the website with Firefox when that redirect was in place (for example if your clients didn't visit the website at that time), then they just load the current website from the webserver as expected. AFAIK Chrome has the same behavior: If you would have visited the website before with Chrome, you would also see the misleading cached redirect behavior. We're planning to take a look at the caching behavior in Bug 968273, to make redirects received over the insecure http (as opposed to https) not permanently cached. That will help with situations like this. If you need to create temporary redirects during development, you can use the status code `307 Temporary redirect` [[1]](https://developer.mozilla.org/en-US/docs/Web/HTTP/Redirections#temporary_redirections). That one wouldn't get cached and the browser validates it on every visit.