Hi I am new to ocotber cms. I have observed that after I logout(page redirects to home page), when I press back button the page redirects to the last visited secured page.
However when I click on any of the link on that page, the page refreshes and redirect again to home page.
I don't want secured page to be seen again after logout. How to achieve this.
I have seen a similar query - after logout click on back button cache issue
but the query was asked 6 years ago and there is lots of information to grasp.
I have a website with https protocol and I use user plugin.
Is there a way in october cms to stop viewing secured page after logout. Or are there some steps I missed?
Related
i'm new to NUXT 3 and i created a small app.
If i'm not logged in, the page always redirect to my start page.
An authenticated user can access the page and can see all subpages.
Now, i want to create a FAQ page and a registration page.
How can i avoid these pages from redirect?
This pages should also be visible without login.
The website is developed in WordPress. It looks perfect on chrom/Firefox browsers but its not looking perfect on safari browser
Can someone help to understand what it the issue and how can i fix it?
If Safari doesn't load a page or webpage items are missing
Check Safari extensions, or try removing cookies, cache, and other website data if a webpage or site doesn't load on your Mac.
Use the steps in this article if this happens in Safari on your Mac:
You can’t log in to a secure website.
A webpage repeatedly reloads or redirects.
A message on a webpage tells you to remove or reset cookies.
Some images, videos, or other items aren't displayed on a webpage, but other page elements load.
Check Parental Controls
If you're logged into a user account that is restricted by Parental Controls or other web filtering software, some pages or page elements might not load if those sites aren't allowed. For example, embedded videos might not display if they're hosted on a site other than the one you're viewing.
Check with your administrator to see if you can get access to the site that you're trying to view.
Check Safari extensions
Some Safari extensions that block ads or other website content can prevent some page elements from displaying. You can temporarily turn off extensions, then re-load the page to see if this is the issue.
Choose Safari > Preferences.
Click Extensions.
Select an extension, then deselect the checkbox "Enable… extension." Repeat this step for every extension that's currently installed.
Reload the page by choosing Choose View > Reload in Safari. If the webpage loads correctly, one or more extensions was blocking the content from loading. Re-enable an extension, then reload the page again to determine which extension is blocking the content you want to view.
If the website still doesn't load with all of your extensions disabled, try the next steps in this article.
If Safari doesn't load pages from a specific site
If only one webpage or website isn't working, you can remove data related to that site to see if it fixes the issue. Use these steps to remove cookies, cache, and other data stored by Safari for a specific site:
Choose Safari > Preferences.
Click the Privacy icon.
Click the Details button.
Search for the name or domain of the website whose data you want to remove.
In the results list, click the domain (like example.com) that has data you want to remove.
Click Remove.
When you're finished, click Done and close the preferences window.
remove history, cookies, cache, website data, for a specific site
If you used the Private Browsing feature of Safari when visiting a website, you might not see the site listed here.
If Safari doesn't load pages from multiple sites
In OS X Yosemite, you can delete website data for the past hour, or past few days if websites or pages stopped loading recently.
Choose History > Clear History and Website Data.
In the sheet that appears, choose the range of data you want to remove from the Clear pop-up menu.
Click Clear History.
remove history, cookies, cache, website data
If you want to remove website data for all of the sites and pages you've ever visited, choose "all history" from the Clear pop-up menu. The option to Remove All Website Data in the Privacy pane of Safari preferences does this, too. These options also reset your browsing history and Top Sites.
I have the following very specific bug in my web application, caused by a curious interaction between the History API and the way Chrome caches pages.
User A logs in and uses a page like /home on the site. This page is an SPA type page that uses the History API to maintain a history stack as you navigate within the page. So as you do stuff, the url may change to /home/with/new/state This page also has a message like "Hello, User 1" on it.
User A logs out of the application.
On the same computer and browser, User B logs in and goes to /home, /home/with/new/state. Again, this is not a true navigation, just modifying the url via the history API.
User 2 clicks some link to navigate (for real) to another page on the site.
User 2 clicks the back button
The browser goes back to /home/with/new/state, but to the cached version that still says "Hello, User 1" on it.
Naturally, this is really confusing for users.
I can fix this by setting a more aggressive cache-control policy, forcing a reload of the /home page, but that would increase bandwidth to the site. The vast, vast majority of the time, the existing caching is fine, because the user isn't changing, so I don't really want to do this server side, for all users, always. It also is only an issue in Chrome; somehow the other browsers handle this correctly. I'd prefer a mechanism to bust the cache ONLY when I have this situation of a user change.
How might I accomplish this?
We have an existing live MVC 4 website that works exactly as it supposed to, running in an Azure Web Role.
A third party want to embed our site in an iFrame on their site (a small part of it anyway, one form really)
I'm no fan of iFrames but this is what they want to do and our business are happy for them to do it.
Except it doesn't seem to work at all.
So I tested it myself with an html page just running on my machine.=, with just an iFrame and a link to the site.
The default page loads fine. It is a forms login screen, when I submit a login, the site crashes into the exception handing and it doesn't provide much useful information.
I then tried pointing the iFrame at the site running in my dev environment. Submitting the login and debugging into the action, the code flows through correctly, no error and tries to return the correct view, but iframe refreshes to the login screen again.
What could be causing this? What am I missing?
I'm working on a Rails 3 application that uses devise for user authentication. I would like the user to only see the splash/signup page when they first visit the site but be sent to the login page if they log out or time out, as follows:
Splash page
Click on login link
Login page
Supply proper login credentials
User's dashboard
Click on logout link or user times out
Login page (not splash page)
Take a look in the devise wiki: How To: Change the redirect path after destroying a session i.e. signing out