Screened Subnet (DMZ) causes Web Service to fail

[Karl A Mikesell]

The underlying connection was closed: Unable to connect to the remote
server. Results when trying to consume a Web Service that sits between
multiple firewalls.

The server returns SOAP request is using the HOST Header of any one of the
firewalls, and not the header information from the original request. ISA
Server can forward this information but other firewall cannot, so can an
addition parameter be added that contains the SOAP return path and override
this default behavior?

Does WSE address this problem?

Any help please.

Karl Mikesell

[Jian Bo]

The short answer is Yes

WS-Referral and WS-Routing are intended to provide return path

Cheers

Jian B

----- Karl A Mikesell wrote: ----

The underlying connection was closed: Unable to connect to the remot
server. Results when trying to consume a Web Service that sits betwee
multiple firewalls

The server returns SOAP request is using the HOST Header of any one of th
firewalls, and not the header information from the original request. IS
Server can forward this information but other firewall cannot, so can a
addition parameter be added that contains the SOAP return path and overrid
this default behavior

Does WSE address this problem

Any help please

Karl Mikesel