How to Redirect to another website on the same location

[glezaber]

Hi, I´ve two websites stored in IIS 5.0, and what I want is to
Redirect from A website to B website, the problem is that doesn´t work
because if I use Response.Redirect (http://localhost:5080) where is the
A website from the B, it only works in the same machine, because if you
try doing it from another one it takes de localhost directly without
asking for the correct parsing. I tryed too doing it with the
Server.Transfer, but that doesn´t work any more.

Any ideas?

Thanks!

 

[Gozirra]

Maybe I'm confused. But if you want to go from site A to site B, why
not just use the proper URL. Assume Site A is @ http://webserver:80
and site B is @ http://webserver:5080.

To go to B - Response.Redirect("http://servername:5080")
To go to A - Response.Redirect("http://servername:80")

If you are worrying about these values changing then toss them into the
config file. Then you can deploy a production version and have one for
testing.

 

[glezaber]

Thanks for your reply, I´m not quite sure, I´m new in asp.net, but
perhaps I have not been clear.

This is how the IIS lookslike

LocalMachine

---WebsiteA (localhost:5080)

---WebsiteB(localhost:80)


The WebsiteB has been registered by DNS so you can access from remote
computers, but what I want is to redirect to WebsiteA when you click in
a webform of site B. As I said it works with
Response.Redirect(http://localhost:5080), but only locally, if you try
the same from the outside it treats "localhost" as a local variable,
and perhaps the correct way for doing this is using Server.Transfer,
but it doesn´t work anymore.

Thanks again for your attention.

 

[Gozirra]

The target url used in server.transfer must be within the same
application which is why it is failing. Is there a reason why you
can't register the other site with DNS as well? Are these sites
published on the web or are they intranet sites?

Standard practice in this situation would be to use Response.Redirect
which would require that the other site be registered in DNS(you could
also get away with IP address). The only other option that I have off
the top of my head would be to create a webrequest and pull the html
from the resulting call. Then you can send the response back to the
client. I don't believe that this will work if the application
requires user interaction.

Why do you need to do this?