Ask Question Forum:
Model Library:2025-02-08:A.I. model is online auto reply
C
O
M
P
U
T
E
R
2
8
Show
#
ASK
RECENT
←
- Underline
- Bold
- Italic
- Indent
- Step
- Bullet
- Quote
- Cut
- Copy
- Paste
- Table
- Spelling
- Find & Replace
- Undo
- Redo
- Link
- Attach
- Clear
- Code
Below area will not be traslated by Google,you can input code or other languages
Hint:If find spelling error, You need to correct it,1 by 1 or ignore it (code area won't be checked).
X-position of the mouse cursor
Y-position of the mouse cursor
Y-position of the mouse cursor
Testcursor
caretPos
Attachment:===
Asked by Spikeuk30
at 2024-07-20 13:42:28
ModifyPoint:500 Replies:4 POST_ID:829042USER_ID:11947
Topic:
Microsoft IIS Web Server;Web Servers;Miscellaneous Networking
ok im moving some live websites to a new server. both HTTP sites and HTTPS port 80 /443
The client wont be able to make any dns A record changes until a few days later so I need to forward on requests from old webserver.
This is a Windows server 2008 / IIS7 webserver.
For example. www.test.com A-record points to 195.123.456.4
New web server has the website configured listening on 217.45.22.15
So I want requests going to 195.123.456.4 forwarding onto 217.45.22.15 seamlessly while still using the www.test.com url (without changing A-Record.)
I think this can be done with IP routing? BUT I have multiple other sites listening on port 80 on the same 195.123.456.4 IP address on the old webserver which need to remain there until a later date.
Any help would be greatly appreciated..
The client wont be able to make any dns A record changes until a few days later so I need to forward on requests from old webserver.
This is a Windows server 2008 / IIS7 webserver.
For example. www.test.com A-record points to 195.123.456.4
New web server has the website configured listening on 217.45.22.15
So I want requests going to 195.123.456.4 forwarding onto 217.45.22.15 seamlessly while still using the www.test.com url (without changing A-Record.)
I think this can be done with IP routing? BUT I have multiple other sites listening on port 80 on the same 195.123.456.4 IP address on the old webserver which need to remain there until a later date.
Any help would be greatly appreciated..
Author: Spikeuk30 replied at 2024-07-22 09:50:00
ok I have used IIS url rewrite setup a reverse proxy in a couple of clicks which seems to work flawlessly with HTTP and HTTPS. I have yet to do some more testing to confirm its working properly....
...as I am proxying to an IP the receiving webserver isn't getting the url sent over, so the bindings for the website on the destination server need to exclude a url so it listens on the IP address and not the url.
...as I am proxying to an IP the receiving webserver isn't getting the url sent over, so the bindings for the website on the destination server need to exclude a url so it listens on the IP address and not the url.
Author: Spikeuk30 replied at 2024-07-20 23:35:08
195.123.456.4 trouble is on other old IP there are also other sites listening on the same IP in IIS which need to remain on pointing to old webserver...
Expert: Lieven Embrechts replied at 2024-07-20 13:52:20
If you have a hardware firewall in between your servers and your ISP, you could just use a NAT rule to forward traffic for the old IP on port 80/443 to the new server.
Expert: duncanb7 replied at 2024-07-20 13:49:57
The instruction for HTTP redirect on IIS 7 is shown on Microsoft website
at http://technet.microsoft.com/en-us/library/cc732969(v=ws.10).aspx
Duncan
at http://technet.microsoft.com/en-us/library/cc732969(v=ws.10).aspx
Duncan
