Well, you redirect with Response.Redirect method. Depending on whether the
authentication is set up, you could do:
Response.Redirect("Http://username:password@othersite/otherpage.aspx");
-- Peter
http://www.eggheadcafe.com
unBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder: http://www.blogmetafinder.com
> Hi
>
[quoted text clipped - 12 lines]
>
> Suresh
sureshpandi - 07 Nov 2007 19:47 GMT
Thanks Peter
I read some article like that
"Microsoft released a security patch that disables passing the credentials
in the url.."
I have tested and it is not working if i pass credentials thru URL.
Someone suggested to use the following,
Page.Response.AddHeader("AUTH_USER", "User")
Page.Response.AddHeader("AUTH_PASSWORD", "password")
Server.Transfer("default.aspx")
The above is also not working for the case
Server.Transfer("http://siteb/onlinedocs/webpage.aspx")
It will be helpful if you give me any other way to redirect to different
site using basic authentication.
Thanks
Suresh
> Well, you redirect with Response.Redirect method. Depending on whether the
> authentication is set up, you could do:
[quoted text clipped - 21 lines]
> >
> > Suresh
there is no way to do this without a custom browser.
the most common approach is to pass a login ticket in the url to site b,
then they call back to site a to get the credentials. site b would still
not be able to use basic authentication.
the second approach is to reverse proxy site b. instead of redirecting,
your site fetches the site b page (with basic authenication) and
forwards them. your reverse proxy will usually have to edit the html for
any embedded url's if they refer to site b's domain name (also /path can
give problems).
-- bruce (sqlwork.co)
> Hi
>
[quoted text clipped - 12 lines]
>
> Suresh