Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I finally found the issue and i fixed the rampart_in_handler.c:91</p> <p>The issue was coming from the response and not from the request... I Inspected through a tcp sniffer and the response from the partner WS was made without any soap:Header. </p> <p>Compliant or not with standards, with the last release ( 2.0.0 ) it was working. So i decided to tweak a little bit the code in rampart_in_handler.c file to return a success in the case of soap header is missing... </p> <p>In my opinion and PLZ correct me if I'm wrong : </p> <p>The test on the soapHeader response was added certainly b/c of the asymetricBinding transport and the new signed usernametoken case. However, if we want to use usernametoken without signing ( <em>through the basic policy.xml</em> ) <strong>AND</strong> the response is made without any soap:Header ; then rampart will always return a failure... </p> <p>Also, i analysed the php code under the scripts/ folder regarding the way wsf handle the response and i saw on this file : <code>wsf_wsdl.php</code> under the function <code>wsf_process_response()</code> : </p> <pre><code>if($response_header_string &amp;&amp; !empty($response_header_string)) { $header_dom = new DomDocument(); $header_dom-&gt;preserveWhiteSpace = FALSE; $header_dom-&gt;loadXML($response_header_string); } </code></pre> <p>Meaning on the php side, when the data are received, wsf/php assume a case without any soapHeader... ( there is no failure if the soapHeader is missing ) Super weird !? </p> <p>At last but not least, i found a weird bug on both <code>wsf_wsdl_serialization.php</code> and <code>wsf_wsdl_deserialization.php</code> files. </p> <p>For instance if you plan to send and/or receive params/values with a string like that : </p> <pre><code> "110% Sigma of something" </code></pre> <p>It will fail and create a segfault during serialize/unserialize process ! </p> <p>Now i'm wondering myself why ? But at a first view, for sure, "110% Sig.." contain "% S" and it's pretty closed of "%s"... </p> <p>I think this bug is this one mentioned here : </p> <p><a href="http://old.nabble.com/WSF-PHP-server-segfault-on-wsf_wsdl_serialization.php---td24329956.html" rel="nofollow">http://old.nabble.com/WSF-PHP-server-segfault-on-wsf_wsdl_serialization.php---td24329956.html</a></p> <p>If i change the S by D or anything else it works...</p> <p>What a pain...</p>
    singulars
    1. This table or related slice is empty.
    1. POWS02 / WSF PHP 2.1.0 UsernameToken issues
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USEsteban Kiteboarding
    1. USEsteban Kiteboarding
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWS02 / WSF PHP 2.1.0 UsernameToken issues
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload