How do you get a web app to not show the 'page has expired...' error and
refresh and requery when you hit the back button after submitting a form I
just want the old data to still be displayed in the form.
I checked knowledge base for this and I do not have "Do not save encrypted
pages to disk" checked and am running IE
6.0.2900.2180.xpsp_sp2_rtm.040803-2158.
"Warning: Page has Expired The page you requested was created using information you submitted in a form. This page is no longer available.
As a security precaution, Internet Explorer does not automatically resubmit your information for you.
To resubmit your information and view this Web page, click the Refresh button. "
I'm developing an e-commerce site from scratch.
I've noticed on other e-commerce websites that use other development tools such as php or probably "websphere" (java) that when clicking the back button this message appears during a checkout process. This is good because it reduces customer error in many ways.
I'm using ASP and response.redirect mostly. But, I've noticed that even setting a page timeout to zero won't stop the caching of the page. My customer, who just submitted a form, can just click the back button and the cached page just comes up.
I have page for user to update his/her details. What i want is after idle for more than 20 mins, the page will redirect to login page automatically. So that the user knows that his/her session already expired and need to login again.
But it doesn't working. This is because if he/she update the details (after idle more than 20 mins), and click the Submit button, it will go to login page and all the data will be lost. Code:
How do you get a web app to not show the 'page has expired...' error and refresh and requery when you hit the back button after submitting a form? I just want the old data to still be displayed in the form so the user can go back, make a few changes, and submit again.
I checked knowledge base for this and I do not have "Do not save encrypted pages to disk" checked and the user is running IE 6.0.2900.2180.xpsp_sp2_rtm.040803-2158 I am running server2003 and IE 6.0.3790.0 update version 3283 and I don't have the problem.
I want to show users a custom "Page Expired" page when users go back to the previous page by clicking the "Back" button of the browser (or when he right-clicks anywhere on the current page & selects "Back" from the menu). How do I do this?
I have a form that users fill in and the results are put into a DB by an asp script, this script will then redirect the users to another page where a receipt number is generated and displayed. How can I make the form expire after the user sends the information and the receipt is issued.
At the moment I am getting the following Expired Warning if a user logins into a secure page and attempts to press the 'back' button:
Warning: Page has Expired The page you requested was created using information you submitted in a form. This page is no longer available. As a security precaution, Internet Explorer does not automatically resubmit your information for you.
To resubmit your information and view this Web page, click the Refresh button. Is there someway to gracefully stop this from happening...in other words.to re-display the login page? Also, what is causiing this? Session Variables?
I have a web pagewhich queries a db and displays information on the subsequent page. On the subsequent page if I click back to previous page (this is a button with javascript code on it), it takes me to the previous page but the page says - "warning page expired".
When I am in my company work environment, I dont get this page, it properly displays the information on the previous page but when I go to the client site, it gives me the problem All of us are on the same IE version and service packs. Could this be a programming issue or a security issue.
I have 3 ASP pages. Page1 has file upload feature where the user selects a file and clicks on upload button. Page2 takes that uploaded file and process the records to insert into the database. Page3 shows that records from the database. Code:
I have a registration page where people sign up for different tennis leagues. However after they're done, they change their minds and use the back key to backup a page and either add or change their selections which ofcourse messes up registrations completely since it was written to the database already. BIG FAT COLORED letters do not prevent them from doing this, neither do they read any instructions. (Which I probably should know by now....) I need to prevent them from doing this by expiring the pages. Both these sites are using asp pages, but the one site is linking to an MS SQL database and the other to an Access.
I want to close the window without the warning "internet explorer is trying to close..." being displayed. I want to do this with vbscript. I found out that in javascript you can do it by including window.opener='x' followed by the window.close statement.My code is: Code:
Response.Write "<script type=""text/vbscript"">" Response.Write "MsgBox ""Hi. see you again""" Response.Write vbcrlf Response.Write "window.close" Response.Write "</script>"
I am writing a web app using asp.net 1.1 and C#. This web app is launched in another win32 application and this app needs to pass information to my web app. But this win32 application doesn't support long string(Maximum 255)
I hv to use an intermedia plain file and in my web app,usingScripting.FileSystemObject to open the file and read the information in. Each time when I launch the web page, I got a warning message saying "AnActiveX control on this page might be unsafe to interact with other parts of the page. Do you want to allow this interaction?" Users need to click Yes to proceed.
All applications run in Intranet environment within a corporate network. My question are "Can I avoid this error message?" and "Can I give permission to my particular web app to run Scripting.FileSystemObject?"
I asp.net pages that run on an intranet IIS server. Some op the pages use XLM DOM doc.Load(sPath) to open and parse a XML file. Every time the doc.Load(sPath) executes in IE6 a warning message comes up "This page is accessing information that is not under it's control. . . "
How can I avoid this message. It is a great anoyance to the users. Do I need to create some time of certificate to pass...
Do you know how to reset session.timeout after user click to extend the session timeout? For example, default session.timeout is 20 mins and 2 mins before will ask whether extend working on the site or logout.
when the senssion ends a message box pops up and alerts the customer that it has ended, but I would only know how to do it after they reload the page or soemthing to check if the session ended. Anyone know how to make a msgbox pop up as soon as the session ends? Also in IIS, is there a place where you can set the sesssion length?
Currently i working on a project using ASP.net and mysql. these are the classes i imported:
<%import Namespace="System.Data" %> <%import Namespace="MySql.Data.MySqlClient"%> Sub Page_Load(sender As Object, e As EventArgs)
Dim myConnection As MySqlConnection Dim myDataAdapter As MySqlDataAdapter Dim myDataSet As DataSet
Dim strSQL As String Dim iRecordCount As Integer
myConnection = New MySqlConnection("server=myserver; user id=XXX; password=XXXX; database=XXXX; pooling=false;")
when i try to test it out on my localhost, i got this error compiler page:
(warning BC40056: Namespace or type specified in the Imports 'MySql.Data.MySqlClient' doesn't contain any public member or cannot be found. Make sure the namespace or the type is defined and contains at least one public member. Make sure the imported element name doesn't use any aliases.
Having some problems updating a recordset, despite the fact that I've used the bulk of the code sucessfully in other projects. I seem to be able to add records no problem, but when I try to update them I get Code:
I have a count down and a body onload linked to a function that closes the connection on my main page to ensure no user will not leave the page without logout.The problem is that my main page opens several others which I´d ike to close as well after logout.Can I rely on If sessionID="" to close those windows?
I have a application which is a global login for other applications. Basically application A checks all the user login information and then lists all the applications B-Z that the user has access to.
I have a global.asa file in application A and individual global.asa files in applications B-Z. Applications B-Z are under the Application A directory. Can I have global.asa files in each of the application folders? Does the pages look for the closest global.asa file?
I have to keep track of user login time and logout tme for each application. The problem I run into is how do I record the user logout time when the session expires?
When i pulling weekly report from the system which using ASP as programming language and SQL Server 2000 as database, an error pop up showing that "Timeout Expired". The report supposes in Microsoft Office Spreadsheet. I tried to query the same stored procedure using Microsoft Query Analyzer and it works. I am not sure what's wrong.
We have a web application where we want a user to be able to change his/her password if the password has expired but we are unable to do this with ASP at the moment because we can't log the user into the database without a valid password.
We do not want to store any "admin" user info to connect to the database to change the users password for security issues.Does anyone have any ideas of how we could go about doing this?
how i can build a script to list deleted domains ? then obviously i can add more features on from there, ive looked everywhere and all of them seem to be php so i cant see how they do it.
I installed ASPUpload component evaluation version on my personal computer for development and testing purposes and now one month has completed, and the component has expired.
I re-installed evaluation copy but it didn't work.
I have a web page displaying results from a query including 4 table joins (so pretty slow anyway). I keep getting the following error message
Microsoft OLE DB Provider for SQL Servererror '80040e31'
Timeout expired /it/fees.asp, line 310
I have the following at the top of my fees.asp page:
<% Server.ScriptTimeout = 300 %> and have also set the ASP Script Timeout to 300 seconds in IIS, Home Page, Configuration, Options. I get the above error message after approx 45 seconds and the query should take approx 1 minute to run.
I am getting the error Time out expired , I have tried every thing increased Server.scripttimeout to 90000 response.buffer=false .. etc even then I m gettin the error.
Microsoft OLE DB Provider for ODBC Drivers error '80030e31' [Microsoft][ODBC SQL Server Driver] Timeout expired
/poststatuscheck.asp, line 39 <-- this would vary
So I searched and found that changing this
cOperations.Open ("DSN=Operations; user id='uname'; password='password'")
to this
cnOperations.Open ("Provider=SQLOLEDB; Data Source=x.x.x.x; Network=DBMSSOCN; user id='uname'; password='password")
makes it work like its suppose to.
The questions I have are...
What is the difference between these two types of connections? I know one uses data source and the other dsn.
Should I be concerned about security with this new method? Should I be concerned with anything in this new method? Is it possible to fix the old method?