header <To>

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jan Hruz - 09 Aug 2004 10:17 GMT

Hello,

I tried to use TCPMonitor which redirects all request from port 8080 to 80.
I changed URL to
http://localhost:8080/UsernameSignCodeService/UsernameSigningService.asmx
in UsernameToken sample.
WebService raised :
Destination Unreachable ---> System.Exception: WSE816: The <To> header must
match the value of an incoming message's HTTP Request Url if the soap
receiver does not have an actor name. The <To> header received contained

I know that I would be able to fix this by adding new URI to routing (?
maybe), but my question is :
How can I turn off validation of some (or all) headers elements like <To> ?
I was thinking about using custom input validation but it doesn't work and
it looks that input custom validation is only additional validation to basic
validation.

Why do I need it ?
There is for example JAVA implementation which adds only wsse:Username,
wsse:PasswordUsernameToken. Now calling of webservice failed because it
didn't find other elements.

Thanks for all answers,
Jan

Reply to this Message

Softwaremaker - 09 Aug 2004 10:32 GMT

There could be different hacks to this. Are you using WSE2.0 on your
Service. If you are, set the SOAP Actor attribute to
http://localhost:8080/UsernameSignCodeService/UsernameSigningService.asmx

Your TCPMonitor will just forward the calls from
http://localhost:8080/UsernameSignCodeService/UsernameSigningService.asmx to
http://localhost:80/UsernameSignCodeService/UsernameSigningService.asmx. The
<To> element should remain unchanged and will be matched with
the SOAP Actor of the Service end.

Have you also thought of using an intermediate Router to do this with
WS-Referral and HTTPSoapRouter to do this instead of using a TCPMonitor ?
WS-Referral will automatically redirect all 8080 port calls to port 80.

The EndpointReference.Via is also another way you may want to look at where
you can send messages to a same SOAP Actor *interface / implementation* via
different transport mechanisms. You may want to refer to Hervey's [MSFT]
blog here for a clearer explanation on what EndpointReference.Via does.
http://www.dynamic-cast.com/mt-archives/cat_wsaddressing.html.

hth.

Signature

Thank you very much

Warmest Regards,
Softwaremaker
Architect | Evangelist | Consultant

+++++++++++++++++++++++++++++++++

> Hello,
>
[quoted text clipped - 21 lines]
> Thanks for all answers,
> Jan

Reply to this Message

Jan Hruz - 09 Aug 2004 11:28 GMT

Thanks for answer. It works.
Is there any way how to avoid or to turn off the validation of wsse header
elements ?
For example by setting some custom validation, policy or overriding some
method of WebServicesExtension ?

Jan

> There could be different hacks to this. Are you using WSE2.0 on your
> Service. If you are, set the SOAP Actor attribute to
> http://localhost:8080/UsernameSignCodeService/UsernameSigningService.asmx
>
> Your TCPMonitor will just forward the calls from
> http://localhost:8080/UsernameSignCodeService/UsernameSigningService.asmx

> http://localhost:80/UsernameSignCodeService/UsernameSigningService.asmx. The
> <To> element should remain unchanged and will be matched with
[quoted text clipped - 16 lines]
> 80.
> > I changed URL to

http://localhost:8080/UsernameSignCodeService/UsernameSigningService.asmx

> > in UsernameToken sample.
> > WebService raised :
[quoted text clipped - 19 lines]
> > Thanks for all answers,
> > Jan

Reply to this Message

Lucien - 09 Aug 2004 22:05 GMT

You can't turn it off. It was added for security reasons. You could create a
custom filter to remove WS-Addressing headers but not something I'd
recommend (especially since using Via is the proper way to fix this).

> Thanks for answer. It works.
> Is there any way how to avoid or to turn off the validation of wsse header
[quoted text clipped - 6 lines]
> > There could be different hacks to this. Are you using WSE2.0 on your
> > Service. If you are, set the SOAP Actor attribute to

http://localhost:8080/UsernameSignCodeService/UsernameSigningService.asmx

> > Your TCPMonitor will just forward the calls from

http://localhost:8080/UsernameSignCodeService/UsernameSigningService.asmx

> to
> > http://localhost:80/UsernameSignCodeService/UsernameSigningService.asmx.
[quoted text clipped - 47 lines]
> > > Thanks for all answers,
> > > Jan

Reply to this Message

header <To>

Free Magazines