The most common case is the server enforce some rules by associating a policy (according to the ws-policy spec) to a service. In that case the server is expected to validate the request with the policy, probably what you too want to happen.

Thanks
Dimuthu

Thank you for the quick and clear reply.

What I need to handle is a custom header indeed, so the “custom mustUnderstand” solution you advice is the way to go.

Truth to tell, the whole concept seems of little use when applied to custom headers … if you put them there, it’s because you need to handle them anyway, while you are entitled to silently ignore any “unknown” custom header you may receive, isn’t it?

Have a nice day,
Massimo

In WSF/PHP, we are only allowing you to write business logic in PHP. But doesn’t allow write Handlers in PHP. So whenever you set some custom handler to be ‘mustUnderstand’ true, then the default handlers in WSF/PHP will not understand it and fails before hitting your php logic.

This can be solved by allowing PHP users to write handlers in PHP. But this will surely complicate the current PHP API.

And the other solution (which I recommend) you can do is use a custom mustUnderstand attribute like ‘MyMustUnderstand’. I’m saying this because you are more likely writing a non-standard custom header. The whole point of using ‘mustUnderstand’ attribute is the interoperability with systems like .NET and other Java Frameworks. WSF/PHP already interop with these systems in terms of Security, RM. Your custom header will anyway not be there in other WS frameworks unless you implement it specifically.

In a case you actually writing a standard header that is not supported in WSF/PHP, then it is always better you write it in C as an Axis2/C handler.

This is just my thought. It is up to you to choose a good approach.

Thanks
Dimuthu

I’m currently using WSF/PHP 2.0 and have a problem related to the mustUnderstand option of WSHeader … hope you can lend me a hand.

I modified the provided add_soap_header_client.php so that it sets mustUnderstand to 1 (true), but now the called echo_service.php returns “Soap Fault: Header not understood”.

According to http://wso2.org/library/tutorials/understand-famous-did-not-understand-mustunderstand-header-s-error
one should provide a custom handler for the header and set a “processed” flag, but the article is geared to Axis2 and the samples do not directly apply to PHP.

So my question is: how do you write a server-side PHP script to handle request headers with the mustUnderstand option set to “true”?

SOME VALUE HERE
SOME VALUE HERE

(…)

but i have to do it like this:

SOME VALUE
SOME VALUE

(…)

I tred to search some solution for having such requests, somone had the same problem but noone could help him. Albo there’s no answer for this in tutorials etc. Could You help me?