Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6543555
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T11:21:40+00:00 2026-05-25T11:21:40+00:00

I have a feature in an ASP app where a user can log in

  • 0

I have a feature in an ASP app where a user can “log in as” someone else (teachers logging in as students to check interfaces, etc). The problem is when they hit the back button and try to access things as instructors again.

What’s the best way to prevent this? Is there a way of preventing them from going back into those pages? I do checks on individual pages for authorization, but I wonder if there isn’t something more elegant.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-25T11:21:40+00:00Added an answer on May 25, 2026 at 11:21 am

    You have to expire the cache, the following needs to be put on every page that requires authentication:

    Response.AddHeader "Pragma", "no-store"
    Response.CacheControl = "no-store"
    Response.Expires = -1
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have an ASP.Net application which as desired feature, users would like to be
I have an ASP.Net website which has a remember me feature for Login page.
I have a feature which allows the user to create projects and view it
I have a feature in my web app like I have to send mails
I have built an ASP.NET MVC app some time ago, and after a few
Background: I'm writing ASP.NET MVC 3 Web app. I have a List<MyObject> (actually several
I have a asp.net MVC app and I'm trying to get the jqgrid 3.5
I have an interesting situation where I need to deploy an ASP.NET MVC app
I have an ASP.NET 4 web app that is using the Entity Framework to
Background: I have a winForm app that registers a user in the database based

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.