pierrer

Hello

I am developing a Web application that uses the Form Authentication.
At one time, I need to launch a new instance of the browser using
javascript.window.open with the correct parameters.

When I run a test outside of authentication everything works fine. However
when I run the same test inside the authentication umbrella, the application
always redirects to the login page.

Is it possible (and how) to launch a new instance of the browser whithin Web
app that uses the Form Authentication

Thank you very much
--
Pete

nicole calinoiu calinoiu removethis at gmail dot com

This is rather unlikely. If the browser's cookie handling were solely
responsible, it wouldn't matter whether navigation to the target page
occurred in the original window or in a new window. Since the
authentication cookie is presumably conserved during navigation to the page
in which the troublesome window.open call is located, it seems safe to rule
out a pure client-side issue.

nicole calinoiu calinoiu removethis at gmail dot com

What happens if you load the target page "into the frame"? (I'm guessing
this means via a plain old anchor tag hyperlink.) Also, are you using an
absolute or relative URL in the window.open call? If an absolute URL, try
using a relative URL instead. If this doesn't help, could you please
provide the following information:

1. The complete URL (including protocol) of the page from which the
window.open call is made.
2. The complete URLs (including protocol) of all the pages in any frame
hierarchy above the caller page (if the caller page is located in a frame).
3. The exact target URL used in the window.open call.

pierrer

Hello Nicole.
First I thank you very much for keeping touch with me. You know I'm
relatively new development over the Internet so excuse me if I do not answer
correctly to your question.

1- The target page works fine when targetted into the app's frame.
2- The target page also works fine when I use a .NET hyperlink server
control. This controls sets the Target attribute to "_blank", a new instance
of IE is opened and it looks like it shares the Session variables with the
parent.

However I did not find how to draw the page at the expected location on the
screen.
That is why I tried to use window.open: to be able to locate the screen at
the correct location. I also tried window.showModalDialog (which I would
like to use the most because it looks nicer) but then again I have the same
problems as with window.open.

I have one sub-folder in my root. All pages are called with the following
syntax using relative path and not :

AppRoot = "http:/localhost";

Target = AppRoot + "/members/target_page.aspx";

window.open( Target, null, sFeatures );

I hope the explanations above are clear enough. You know I'm French
speaking so if you need more info, please feel free to let me know.

Once again, thank you very much.

nicole calinoiu calinoiu removethis at gmail dot com

Pierre,

The problem appears to be that your "http://localhost" root doesn't match
the base URL for the originating page. There are two possible reasons for
this:

1. The originating page was loaded over HTTPS, and/or
2. The originating page was loaded using a different server name/IP (even
if this also points to the local machine).

Either way, the solution is the same: use a relative URL in the window.open
call. For example, if the originating page is in the directory above the
"members" directory, use the following call:

window.open( 'members/target_page.aspx', '_blank', sFeatures);

If the originating page is inside the "members" directory, just use the page
name:

window.open( 'target_page.aspx', '_blank', sFeatures);

HTH,
Nicole