WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  SOAP WS TRANSPORT CHUNK

    Posted 13 hours ago

    Hello everyone,

    I've successfully signed an XML document using SAAJ, and the digital signature is valid.
    However, when the message is sent through SOAP (using the JAX-WS client inside IBM WebSphere Application Server), the communication still uses
    Transfer-Encoding: chunked, which causes an error on the remote endpoint.

    If I send the same XML manually using HttpsURLConnection, it works perfectly - the request includes a fixed Content-Length header instead of chunked encoding.

    I've already tried the following in my client code:

    

    

    

    

    


    


    BindingProvider bp = (BindingProvider) port;
Map<String, Object> rc = bp.getRequestContext();
rc.put("com.sun.xml.ws.transport.http.client.streaming.chunk.size", -1);
rc.put("http.conduit.client.AllowChunking", "false");
System.setProperty("com.ibm.ws.websvcs.disableCOALESCING", "true");
System.setProperty("com.ibm.websphere.webservices.transport.OPTIMIZE_HTTP_HEADERS", "false");

    …but it seems these properties are ignored in the IBM Axis2-based JAX-WS runtime.

    Could someone confirm the correct way to disable chunked transfer encoding in WebSphere
    and force the client to send the Content-Length header instead?
    (For example, via JVM property -Dcom.ibm.websphere.webservices.useChunking=false or through the WebSphere console.)

    Any guidance or examples would be greatly appreciated.

    Thanks in advance,



    ------------------------------
    Jose Luis Nebril
    ------------------------------


Related Content