Re: asp.net postbacks don't work after leaving browser open all night w/ windows integrated authentication
- From: "Scott M." <s-mar@xxxxxxxxxxxxx>
- Date: Sat, 21 Oct 2006 16:37:54 -0400
I don't know, it seems like it is a server-side authentication issue to me.
Client-side pages are static, if they do something at 7pm, they do it again
at 7am. If that is not happening for you, it is most likely a server-side
problem.
"Ken Yee" <kenkyee@xxxxxxxxxxxxxxxxxxx> wrote in message
news:Xns986267BBC7189kenkyeeyahoocomSPAMG@xxxxxxxxxxxxxxxx
Has anyone seen this?
If you open up an MSIE (latest 6.x) browser window on a web app that is
set to allow only windows integrated authentication, the next morning, if
you click on any of the links (they're trivial asp.net controls like a
hyperlink but it uses postbacks), you'll get cryptic javascript errors
like "permission denied; line 97 character 2" (which references nothing
when you do view source) or "object expected; line 1 character 1".
Closing the browser and opening a new one brings up the web application
properly after you log in...no javascript errors. This tells me that
it's a client-side issue rather than a server-side issue.
I also have MSIE 6.x set to "check pages on every visit" instead of
"automatically" in the cache settings, but I think this is only affecting
web pages and not the windows authentication credentials.
TIA.
ken
.
- Follow-Ups:
- References:
- Prev by Date: Re: Need for encryption in WSE 3.0 if using SS-avoid man-in-middle
- Next by Date: Re: <location> multiple file question
- Previous by thread: asp.net postbacks don't work after leaving browser open all night w/ windows integrated authentication
- Next by thread: Re: asp.net postbacks don't work after leaving browser open all night w/ windows integrated authentication
- Index(es):
Relevant Pages
|