We have a site linked to an SQL dbase, that uses sessions for logged in users.
The site was originally set up to use frames. I have been tasked with removing them.
The problem that I have is this. I have removed frames from the pages used pre-login. This includes the page set as the login page.
The login itself works fine and loads both the header and body frames of the first logged in page, this page loads as - temp_frames_switch.asp which does not exist as a page on the site and is, I presume, created to cope with the transition from no frames to frames. This in itself does not cause problems as the site works fine, however if a user logs out then they are returned to the logon page (default.asp) which is no frames, this loads okay, but if a user clicks the back button on the browser they are returned to the temp_frames_switch.asp page. This puts them in an area of the site they need to log on to access usually, although the session has been ended they are allowed to perform some basic read-only database browsing on the page without problems.
This is not a massive security problem, but needs to be solved. Originally the the address in the address bar on IE always had the page default.asp as the page loaded and on refresh the session ended and the user was logged out.
Has anyone any suggestion on where I should look as I am a bit of a newbie to all this sort of thing.
The site was originally set up to use frames. I have been tasked with removing them.
The problem that I have is this. I have removed frames from the pages used pre-login. This includes the page set as the login page.
The login itself works fine and loads both the header and body frames of the first logged in page, this page loads as - temp_frames_switch.asp which does not exist as a page on the site and is, I presume, created to cope with the transition from no frames to frames. This in itself does not cause problems as the site works fine, however if a user logs out then they are returned to the logon page (default.asp) which is no frames, this loads okay, but if a user clicks the back button on the browser they are returned to the temp_frames_switch.asp page. This puts them in an area of the site they need to log on to access usually, although the session has been ended they are allowed to perform some basic read-only database browsing on the page without problems.
This is not a massive security problem, but needs to be solved. Originally the the address in the address bar on IE always had the page default.asp as the page loaded and on refresh the session ended and the user was logged out.
Has anyone any suggestion on where I should look as I am a bit of a newbie to all this sort of thing.