Using window.open equivalent in firefox causes .NET session variables to go away. Why? How can I fix?
I have an application which runs in Adobe/Apache Flex with a .NET middle tier. To run reports I need them to run in a separate window so I use; navigateToURL(url, "_blank… (čítať viac)
I have an application which runs in Adobe/Apache Flex with a .NET middle tier.
To run reports I need them to run in a separate window so I use;
navigateToURL(url, "_blank"); This works swimmingly in all browsers (IE, Chrome & Edge) except Firefox (FF). The app has been around for quite a while, and I can't imagine that it never worked in FF, but it doesn't with the last couple of releases.
The symptom is that the .NET "Current.Session.SessionID" changes to a new ID for both the original browser window as well as the new browser window. This causes it to lose all session variables, of course.
The problem only seems to manifest itself if I use "POST" to send variables to the popup window. If I use "GET" everything works fine. An added "bonus" is the "Post" parameters being sent to the new window disappear. So my report doesn't run, and the original window "loses its mind since the session ID changes."
As a test I dusted the cobwebs off and created two ASPX pages which did
<form method="post" name="TestForm" action="TestWopen2.aspx" target="_blank">
The problem was not exhibited in that environment on any browser including FF.
This leads me to believe that Adobe Flex (Flash) is mucking things up a bit.