have a website which as far as I know has the following timeout settings:1) In Web.config, FORM's authentication timeout="10"2) In Web.config, MEMBERSHIP's userIsOnlineTimeWindow="10"3) Assigned in Global.asax on Session_Start(): Session.Timeout =10;In the past I had problems because at least 1) and 3) weren't in sync, not sure about 2).
Do these 3 have to be in sync and if so, is there a way to set the timeout once and to have it applied to all 3? I deploy my website to many clients and each may want a different timeout, so I'm looking for a dynamic method to set this, perhaps after loading the timeout period from the db or settings file.
I'm working with ASP.Net web services and am having a problem with a long-running process that takes about 5 minutes to complete, and it's timing out. To fix this, I was able to set the executionTimeout on the server's web.config to 10 minutes, and then set the .Timeout property on the Web Service object to approximately 9 minutes. Now, I'm worried that this may possibly cause some other web service calls to sit there for 10 minutes before they time out rather than the previous 90-100 seconds. I know the default on the client side is 100 seconds, but wasn't sure if updating the server's timeout setting would affect this.
Bottom line is - Is it safe to update the server's timeout setting to a long amount like 10 minutes, and rely on the default timeout on the client, or could this end up causing some problems?
Is there any way to stablish a global timeot when calling webservices from Javascript in an ASP.NET application?Now the only way I know is setting the timeout manually for each service: service1.set_timeout=100000;
VWD 2008 Express. IIS 6.0. Forms Authentication.My web site uses forms authentication (in case that makes a difference). Folks who are using the site indicate that it is timing out on them (logging them out) before they can finish some entries. How can I increase the timeout period? The following is my web.config file in my root directory:
[Code]....
Here is the web.config in the subdirectory to which all users are directed at login:
I am using Asp.net 2.0 and C#.I have 2 webpages, which contain lot of questionnaires. I have a submit button in my 2nd web page. I want to set a timer in the page, so that after 2 minutes, if the user has not completed the questionaire, i want to click on the submit button automiatically.
I have a site that when a user logs in it sets their initials into a session variable and sets the timeout value like so:
[Code]....
I want the user to be logged in for 3 hours. This does not work, the session expires after a short period of time, maybe 20 minutes. What do I need to change to make this page level validation work?I have tried setting in web.config also, but this doesn't work either.
The constructors for manually creating FormsAuthenticationTicket objects force us to set an "expiration" value, and this value overrides the "timeout" setting in web.config in my tags, which is not what I want, because now the user doesn't timeout. The "session" just expires at the given time.I need to manually create my ticket for UserData reasons, and it is just the way I decided to build my app. I guess I could spend a whole lot of time and redo the way my app. authorizes, and store the "userdata" elsewhere... but this seems extremely tedious for something so small..Is there anyway to manually create an Auth Ticket and still maintain timeout settings?! And by timeout, I mean resetting the timer on user activity. Not a fixed timeout!
I want to allow admins to be logged in for longer than normal users. I don't see a hook for setting the cookie timeout programmatically or in a role-based way. Is this possible in ASP using Forms Authentication?
i am working on an application ,i have hosted on server. everything going fine . i have added a code to set session timeout in webconfig . but its expire default time .
We have the timeout value set to 120 in our <form> tag within the web.config. We do not have a session timeout set.. and we have various connection strings.
We are having a problem where a session variable will disappear (become NULL) .. but, the form evidently remains 'open'.. or no re-login is required..... so, my question(s):
1. what is the relationship between form timeout and session timeout
I have implemented the basic forms authentication.In web.config I have set the following, in the authentication tagtimeout = "50000000000" Other than that, I have an out-of the box implementation.I have no custom provider.My clients want to pretty much enter the username once a day.The timeout is in minutes, so I am sure that they are not waiting over 5 million minutes,so something else has to be booting them.
The reason why I use "inline" instead of "attachment", so I can force the users to view the PDF directly in the browsers instead of opening up the acrobat to view the PDFs. Everything is fine so far, but when users want to save a file, the file name which should be set to "getFileName(DateTime.Now)", instead it just takes the name of the page like myPDFpage.pdf.
Is there anyway, without setting the content-disposition to "attachment", for the users to save the file with the name I specify with the getFileName() method?
We have an ASP.NET 2.0 site in which we use ASP.NET login / authentication controls.
Our users currently timeout after approx 20 minutes, forcing them to log back in, and this appears to be causing downstream errors in our application.
I have tried increasing the SessionTimeout value to 120 mins (<sessionState timeout="120" />) in the site's web.config file, and the "<membership userIsOnlineTimeWindow="5000" >" value in the web.config is set to 5000 minutes.
These are the only values / settings I can think of to affect this behaviour.
We currently have a set of ASP.NET application and we are migrating them to use Windows Authentication (used to be form Authentication). We will eventually let the user to connect to our site entering Windows Authentication credentials. When we tested within our system across different domains, we noticed that the authentication session seemed to be cached even with the server session had timed out. In other words, once the user logged in and keeped an Internet Explorer window up (didn't even have to be in ourapplication page), the user could always navigate back to our application without being prompted for security login again. We had our site included in the Trusted Site list of the IE browser.Is that the expected behavior for ASP.NET Windows Authentication? If that is the case, is there a way to end the Authentication cache when the users leave their IE windows idle.
i have a web service published in the server, which is accessed by others. In this case if the webservice path is changed it cant be accessed. so hw can this be handled. even if i chng the publish fldr the people using it wont be affected.
I have a user control in asp.net that i need to dynmically set properties for. The propety and property values are in a dictionary, for example:
Dictionary<string, string> propertyValues; Control c = Page.LoadControl("~/Control.ascx")
I can currently set the properties on the control using reflection, however, with .net 4 and the new dynamic keyword, is there an easier way to do it, for example, something like this:
So I took over a companies site and are QA department noticed that after the site sets idle(30 minutes) they can still click around until it preforms a database function that is when it errors out. I thought I had the web.config set properly that the user would be logged out after 30 minutes, but they are still able to make clicks on a gridview and popup modal popups. The site uses membership and I have never had an issue in the past with the timeout on forms auth.
My 3.5 app uses Forms Authentication. I create an authentication cookie (ticket) with an expiration date of one day. The cookie's IsPersistent is set to True. I do not use any session variables. Session timeout is the default 20 minutes.
Here's the problem:
When the session times out in 20 minutes, the user is redirected to the logon page even though the authentication cookie has not expired.
Why does this happen? I thought the session and the cookie were independent of each other.
how to redirect to a custom URL on Forms Authentication timeout? The timeout is working but it is only caught when I try to go to a page in my application because each Page_Load method is wrapped in a custom IsLoggedIn method. Here is the settings I have so far in the Web.config.
My client wants 2 separate login pages for an ASP.Net app, one for regular users, one for support staff. I am using the standard FormAuthentication component for authentication. Is it possible to redirect a regular user to one login page after a timeout, and also to redirect an admin user to a different page after a timeout? The loginUrl attribute of <forms> in web.config is read-only, and cannot be edited at runtime.
Regular User -> Timeout -> Login.aspx Support User ->Timeout -> SupportLogin.aspx
I need to configured my web application to display a warning message to the user 5 minutes before the authentication session expires. I found a javascript code that acts as a counter, however I still could not figured out how to make the page to refresh when the user clicks the Ok.
this is the javascript code...
<script type="text/javascript"> var leftime =5; var interval; interval = setInterval( 'change()' , 600000); function change() { lefttime --; if(lefttime<=2) alert("the session will be off, left time is "+lefttime+ " second!") } </script>
