Hostname replacement for outgoing requests
We send messages from an internal app to an external app/webserver (via ISA 2006) where the internal app uses a specific hostname in its http request (we use a Webchaining rule to bridge the http to SSL and we also have an access rule to allow the trafic through to the destination server). This works happilly but we now require the hostname on the request to be changed to a different value (for various reasons I won't go into we can't have our app do this).
I.e. we send a request to URL http://testserver.bob.job.co.uk/blah and the destination requires the request to be https://newserver.bob.job.co.uk/blah. What I suppose I'm looking for is a similar thing to the web publishing rule which allows you to modify the host value sent onto requests for incoming web server requests?
Any help greatly appreciated.
Answers
You can only change hosts headers in web publishing rules.
Basically, you have two choises:
1. reverse-web-publish the external site to the internal network
2. send the request to newserver.bob.job.co.uk and change the ISA server hosts file so that it resolves to the same IP as testserver.bob.job.co.uk
Jim Harrison Forefront Edge CS- Marked As Answer byNick Gu - MSFTMSFT, ModeratorWednesday, October 14, 2009 1:55 AM
- Proposed As Answer byJim Harrison IsaDewd Thursday, October 08, 2009 6:39 PM
You'll have to:
1. create a web listener that operates on an ISA internal IP address
2. create a web publishing rule that uses accepts requests for testserver.bob.job.co.uk and redirects them to newserver.bob.job.co.uk
3. force the internal app to resolve testserver.bob.job.co.uk to the ISA internal IP
Jim Harrison Forefront Edge CS- Marked As Answer byNick Gu - MSFTMSFT, ModeratorWednesday, October 14, 2009 1:54 AM
- Proposed As Answer byJim Harrison IsaDewd Monday, October 12, 2009 5:22 AM
All Replies
You can only change hosts headers in web publishing rules.
Basically, you have two choises:
1. reverse-web-publish the external site to the internal network
2. send the request to newserver.bob.job.co.uk and change the ISA server hosts file so that it resolves to the same IP as testserver.bob.job.co.uk
Jim Harrison Forefront Edge CS- Marked As Answer byNick Gu - MSFTMSFT, ModeratorWednesday, October 14, 2009 1:55 AM
- Proposed As Answer byJim Harrison IsaDewd Thursday, October 08, 2009 6:39 PM
- Jim,
Thanks for this.
Option 1. is what we'd have to do then in our case. I'm in the novice stakes when it comes to ISA, any pointers on how this would work would be greatly appreciated (would the reverse-web-publish rule be instead of the access rule? Presumably it would not affect the chaining rule either as we publish a client SSL cert in this chaining rule?).
Many thanks,
Rich You'll have to:
1. create a web listener that operates on an ISA internal IP address
2. create a web publishing rule that uses accepts requests for testserver.bob.job.co.uk and redirects them to newserver.bob.job.co.uk
3. force the internal app to resolve testserver.bob.job.co.uk to the ISA internal IP
Jim Harrison Forefront Edge CS- Marked As Answer byNick Gu - MSFTMSFT, ModeratorWednesday, October 14, 2009 1:54 AM
- Proposed As Answer byJim Harrison IsaDewd Monday, October 12, 2009 5:22 AM
