Forum Discussion

Mountazar_Abou_'s avatar
Mountazar_Abou_
Icon for Cirrus rankCirrus
Dec 16, 2017

xmlns="" is causing rejection on BIG-IP ASM

Dear sirs, we are facing a rejection by F5-ASM when the below SOAP XML request (received from the client side):

http://schemas.xmlsoap.org/soap/envelope/";

xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

is changed into :

http://schemas.xmlsoap.org/soap/envelope/";

xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

The sole difference is that: xmlns="" attribute was added to the element. Kindly advise on how to solve it, knowing that we do not have control on the sending party program to force it not to insert the [xmlns=""] into the tag.

The error reported is: Malformed document - Schema validation failed

Thanks and regards

application delivery
ASM Advanced WAF
security
  • Mountazar_Abou_'s avatar
    Mountazar_Abou_
    Dec 17, 2017

    Dear sirs, I found the reason behind the rejection.

     

    It was simply because the element is not under namespace ";; and that is why it needs to have an attribute of [xmlns=""] in order to work correctly.

     

    Its parent element (sendOTP) had the attribute of "xmlns=";; thus affecting its child element namespace.

     

  • Mountazar_Abou_'s avatar
    Mountazar_Abou_
    Icon for Cirrus rankCirrus
    Dec 16, 2017

    Sorry sirs,

     

    I was wrong. It is the other way round.

     

    The rejection occurs when removing the [xmlns=""] attribute from the element.

     

    To re-clarify:

     

    works fine

     

    does not work

     

    Sorry for this.

     

    Regards,

     

  • boneyard's avatar
    boneyard
    Icon for MVP rankMVP
    Dec 17, 2017

    did you upload a schema / template XML?

     

    which version of ASM (TMOS)?

     

  • Simon_Blakely's avatar
    Simon_Blakely
    Icon for Employee rankEmployee
    Dec 17, 2017

    Mountazar,

     

    It looks to me that those SOAP request are incomplete, as there are no closing elements for the and elements.

     

    Without the entire request it is difficult to determine if the syntax is valid XML.

     

    Please repost the entire working an non-working request for comparison, and take care with the formatting (enclose the entire request using the code tag) so it is clear exactly what the SOAP request is.

     

    Thanks

     

  • Mountazar_Abou_'s avatar
    Mountazar_Abou_
    Icon for Cirrus rankCirrus
    Dec 17, 2017

    Dear S, I found the reason behind the rejection.

     

    It was simply because the element is not under namespace "; and that is why it needs to have an attribute of [xmlns=""] in order to work correctly. Its parent element (sendOTP) had the attribute of "xmlns="; thus affecting its child element namespace.

     

    Thank you anyway for your willing to help.

     

    Kind regards, Mountazar

     

  • Mountazar_Abou_'s avatar
    Mountazar_Abou_
    Icon for Cirrus rankCirrus
    Dec 17, 2017

    Dear sirs, I found the reason behind the rejection.

     

    It was simply because the element is not under namespace ";; and that is why it needs to have an attribute of [xmlns=""] in order to work correctly.

     

    Its parent element (sendOTP) had the attribute of "xmlns=";; thus affecting its child element namespace.