Last post Sep 09, 2006 04:37 AM by Luis98000
Aug 09, 2006 05:45 AM|Luis98000|LINK
Hi, I'm a new user on this forum.
Here is my problem:
I have an “official” domain www.MyDomain.org that is DNS redirected
to a physical server www.AnotherDomain.net/MyDomain/ .
So if somebody types www.MyDomain.org/anypage.aspx
he gets the correct page automatically at www.AnotherDomain.net/MyDomain/anypage.aspx.
The problem is that the latter address is shown in the address bar
and also search robots don’t have the reference to the “official” address.
I would like to have the asp.NET 2.0 Virtual server I use,
to rewrite the page URL before sending it to the client’s browser in the form:
www.MyDomain.org/anypage.aspx (as said, I already have DNS automatic redirection to the physical site).
This will involve a further redirection for each visited page to the physical real one
I don’t think it’s a problem (for speed or other).
I know asp.NET offers URL RewritePath method feature,
but it seems to me only to apply to the relative internal paths, not to the domain part of the address.
Is there any way to do what I need ?
It seems that asp.NET can do everything with http data, before sending it to the client’s browser,
so why couldn’t change the domain part of the header?
Many thanks for your help: I’m completely newbie in asp.NET!
Aug 29, 2006 11:58 AM|docluv|LINK
two things I can offer. First is a
301 redirect, but I do not think this is what you are seeking to do. I will throw this out just in case you find it useful.
I think you are really seeking to do a true
Sep 09, 2006 04:37 AM|Luis98000|LINK
First of all many, many thanks your answer: I probably didn’t setup correctly the email notification, so I see it just now!
In the while I did my best to understand and study the matter, without any result.
I guess URL mapping/redirect isn’t the solution.
I even ask myself if a solution exist in the real actual context: so I explain in detail the situation and your help will be appreciated if you can
tell me just IF a solution may exist.
Now the facts:
I have realized and maintain the web site for my humanitarian association, AMADE-Monaco you can see at www.AMADE-Monaco.org.
As all the other members, I do it for free, paying also all fees in a way it doesn’t cost anything to the association. But this limits the costs I
can support: I have to do it cheap.
On the other side, I need a reliable solution.
So my actual choice was:
I bought the domain at a cheap provider with DNS and NO physical server.
I use the free DNS service from ZONEEDIT to redirect it to one of three physical (very cheap) hosted virtual servers I bought with different domain names.
This let me to redirect the site to one other server as soon as the one which is in use comes out of service (this already happened at least three
times in 2006, for a few days duration).
This is good for reliability because I constantly check the site and if needed it takes me two minutes to switch to a different server.
In past years I used a cloaked redirection (with an invisible container frame) that let me keep the main official domain in the user’s browser.
Now as long as I try improving the site, this cloaked frame method is put off (I don’t list you the reasons of this choice but you can imagine).
Now my wish is to obtain back the fact of having the official domain address in the user’s status bar, and for the search robots too.
instead of http://www.monaco-377.net/amade-monaco/index.aspx
or http://www.monaco-free.net/amade-monaco/index.aspx (depending on the actual physical server
As said, I already have a 301 redirection automatically from the official domain amade-monaco.org, but the 301 is done at ZONEEDIT server and I have
no control there.
So I said myself that if I could modify the HTTP headers on the physical servers using ASP.net facilities I could have the user’s navigator to always
“see” the official domain instead of the local one, but I’m no longer optimist on that. Maybe it’s impossible.
Things could be easier if I put the official domain on a physical server, instead of using ZONEEDIT, and then just put there an ASP.NET handler to
redirect it (maybe using proxies methods???).
But the problem is: ZONEEDIT is free but highly reliable (no one fault in many years), while the physical server I can get for a very cheap price
are virtual servers who give me many 4 to 6 faults a year!
Maybe a solution is a more complex implementation of DNS (for instance using the free Granite Canyon service) bur I have no knowledge at all in the
field (of course I can try to learn, if somebody tells me there is a solution in that way).
I understand that using more money the problem should not exist: buying a “real” server, with a real own IP, with full access to its functioning instead
of using virtual hosted ones, will let do everything… but I cant afford that solution …
Many thanks for any suggestion you can give me.