I have developed some aspx pages using visual studio 2008. I am authenticating using Active Directory services. I have kept a link button on my aspx page which says signout .What exactly i want to do is that i want the back button of my login page to be disabled so that when i press signout and when my login page loads users cant go back and thus forced to enter the login details. I am using c# as development language.
I've got an asp.net page that uses dynamically populated DropDownLists and OnSelectedIndexChanged events. A few days ago I found a defect where hitting the back button would load the previous page from the browser's cache, so the DropDownList would already have a selected index (hence the OnSelectedIndexChanged event would not fire properly as it didn't have the default selected index). I understood the issue and googled around. It's a well known issue that doesn't have an easy solution because of how the browser interacts with the page. After a bit of thought, I went with a trivial javascript solution to reset the ddls:
var gvTable = document.getElementById("foo"); if (gvTable != null) {
[code]...
This worked well and I was happy. Until I tested it in IE. In IE, it appears to run the script, THEN load the cached values of the DDL. That is, I observe the DDL snapping back to the 0 index, and then suddenly dropping down to the previously selected value. I'm sort of at a loss here, I typically debug in firebug, but this works perfectly in firefox and chrome.
In an ASP.NET 3.5 website we are noticing that the back button is not working properly. If the user does several postbacks (say 10 times), and than starts pressing back button - the back button gets disabled before the user gets through all the pages. The site does not use AJAX.net.
I can reproduce the issue on IE 7 and 8 almost always. The problem seems to be with some sort of limit IE has on History Cache for a given tab/instance. In the tests I did the post request to the server are large - around 83k, and the responses are are round 300k. It seems that with these request sizes the history does not hold more than 4 items. The moment I get to the 5 post, the first item i had selected is dropped.
how can i get around the following problem-i have a drop down list control on one of my pages- ddlEmployeeTypeit lists 1.Perminent2. Contract3.Tempon selected index change, if its contract or temp, then a text box appears where the user need to type in the contract expiry date-so changing from Perminent --> Contract text box appears- but when the internet explorer back button is clicked - the text box dissapears (which is fine) but the ddl does not change it still reads contract i wanted it to revert back to perminent.is there a solution to this problem?
I have a shopping basket on my site, and when the customer gets to the final page I don't won't them to be able to go back i.e. use the back button on the explorer. I have seen it before on other web sites, it's like when you leave the page it 'times out'I am just not sure how that works.
My problem occurs when the user presses the enter key when the input field is in focus. When he presses the enter key the browser automatically fires by default the next button. In my case it is the delete operation.
I have an ASP.NET problem. When I press Back on Internet explorer, the previous page will be appeared. I need to prevent this page form appearing. How can I do this
I have asp button control on my page. Upon running in IE, it is not doing anything even postback. While the same is running perfect in Firefox. I have surfed the web regarding the problems and almost applied all the things. I have no double forms tag. I found one solution to set UseSubmitBehavior="false". After this, it work but my text box controls lose its content. I am using framework 3.5.
I have a crystal report page where on clicking upon internet explorer button i need to show this message.Some time it shows the message and some time it doesn't ??
I'm offering a course and exam online. In the course I want to disable the save as. (When the user clicks save as it should save a blank page). I did it for printing as follows:
Code: <style type="text/css" media="print"> BODY {display:none;visibility:hidden;} </style>
I searched online and couldn't come up with anything. E/o just talks about how bad it is to do that. I know it's not secure and there are many ways to get around it, but for the average user it'll be good.
I'm currently building a simple chat application and I have everything working real smooth except for one thing, and this problem is only in IE as far as I know (in firefox there is no problem).
In my chat application I have the textbox where the user writes the messages to the chat and the button that sends this message togheter in an updatepanel (so that there is no visible postback when pressing the button). I also have in the form tag "defaultbutton=" set to the button. The problem is that when the user uses Internet explorer and presses Enter instead of pressing the button with the mouse that after the 2 first times he/she does this causes the textbox to stop focus on it, which it shouldnt do as in the end of the button the code says it should focus, which works the 2 first times for some reason.heres the code where the problem exists:
aspx:
form id="form1" runat="server" defaultbutton="Button1"> <asp:ScriptManager ID="scriptManager" runat="server">
when i test this page http://www.catalogues4u.com.au/ViewCategory.aspx?catID=119 im getting the above error. to replicate this issue visit the above page in ie7 and you will get the prompt.
I am also facing some issues with Back Button of Internet Browser as well. Actully Page Load event of my page is not firing when i click on Back Button of Internet.
My customer has a website that is unsuitable for children. Anyone under 18 is not allowed ont he site. No, it's not a porn site, it's prison related. A certain page requires the user to enter their birthdate. If they are under 18, they're redirected to another site.
He has another site written for kids who have been impacted by crime. He wants the kids redirected here, to a page that explains why they were redirected. He asked me to disable the back button at this point to keep the kids from easily going back to the original site.
I've read all the reasons why you shouldn't desable the back button, but frankly, I think this would an appropriate place to do it. I also know you really can't disable it, but I've found a number of work arounds - none of which I've gotten to work.
Is there a work around that will work?
I've thought of setting a session variable or a hidden field or an invisible label on the page that redirects the kids just before the redirect and checking the value at page load, but the code to do the checking doesn't get run unless the user hits the back button then refreshes the page. Is there a way to get code to run as soon as the back button is pressed?
Possible Duplicate: Disabling Back button on the browser i want to disable browser back button without using javascript function forward().because it remain on this page.
I want to totally disable browser back button like banking sites
How to disable back and refresh button. I want to know how this can be handled as in bank websites and other secured websites. Can this be handled using clearing cache in Response object?
I'm using 2 masterpages in my project.One master page is for login page and another one for the HomePage where user will go thro the options to reach other pages from home page..The thing is,i have "Logout" button in my home page.When i click on the logout button,the page will be redirected to "LoginPage.aspx". After redirecting to login page,when i click on browser back button,the previous page is displaying but it should not display to user since i'm doing sensitive transactions in all pages...
i want to protect pages from back button of the browser when my customer logout. so i use Response.AppendHeader ("Cache-Control", "no-store"); to clear the cache of my pages to make it checks session each time. however, i also find that if i use some controls with autopost back and this no-cache flag will also cause problem to make the error "webpage has expired" when my users click back button when they have not logged out.
When we click our back button the page only returns to the previous state (un checking the check boxes one by one after each click). We would like it to go back to the previous page and remember the history of the page.
I have used lot of codinds to disable the browser (using server side code) back button in mozila firefox 3.2 it is not working.But it is working fine in the Internet Explorer.
My problem is when I use ASP.net, this button do PostBack, but I not need this because my list of items then gone. How can I override this behavior of button.