To all,
I am having the same problem. And it is NOT an option to make the
javascript app that creates the iframes into a application that spawns new IE
sessions. I HAVE to have the JavaScript somehow FORCE the iframes to use new
sessions.
In my case, I'm trying to make a "master page" control many iframes that
each in turn calls a CGI app. I'm finding that the iframes are ending up
reusuing the same "session" as the "master page", no matter what I do.
If the iframes were working to what I need, then on the server, there
would be another instance of the CGI app launched, and visible under the Task
Manager, for each iframe my "master page" launches.
But with this problem, the "session" is being reused by, and on the server
one can clearly see that the CGI app get laucnhed only ONCE, and each iframe
has to wait for the other, until one by one, each iframe gets a chance at the
server.
I've followed MSDN directions to disable "session", "Session state" in IIS
directly with the Virtual Directory setting by unchecking th "Session"
checkbox. I've used "Session.Abandon" in global.asa in the Session_OnStart, I
used , <%@ ENABLESESSIONSTATE=False %> in a wrapper ASP file that in turn did
a response.redirect, I tried client side document.cookie, I went into IE's
Tools - Internet Options - Privacy, and set "No cookies allowed", and then
some. But despite this, when the CGI app is called from the multiple iframe
objects, IIS queues them all up into a single "instance like" call, where one
using task manager can clearly see the CGI app being called ONCE and only
ONCE for all of the iframes. This causes the iframes to wait around until one
at a time, each gets a chance by IIS to do its work. Strangely though, if I
"refresh" my "master page" while an instance of my CGI app is running, I will
PROPERLY get IIS to launch another.
I've also followed the discussion on the following link:
http://www.experts-exchange.com/Web/..._21085546.html
Please do not ask/state "if you can give us your actual requirements then we
might be able to help you", as like David, I have clearly stated my "actual
requirements".
As for ideas to follow. I think that somehow putting HTTP information into
the URL, one might be able to override IE reusing the same session ID.
Another idea is to use the "Negotiation protocol" in the URL to force each
iframe to use a different domain user id as such:
http://domain%5cuser:password@Server...ectory/App.asp will also FORCE
IE to not reuse the session id, as it won't be able to, but in that latter
case, Microsoft has turned this feature of IE "off" as of XP - SP2, for which
I'm trying to find the MSDN article that denotes how to turn it back on, and
even if on, I would then have to create an account for each iframe, which
would be impracticle.
So, any ideas would help,
