DataPower

DataPower

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.  Failed to process response headers in MPGW

    Posted Tue August 27, 2024 10:08 AM

    Hi Team,

    We are facing issue while calling backend url which is extenal to our network from MPGW. Where it is working fine and giving correct response in error cases like mismatching backend credentials in header, not passing mandatory fields in header. When we are passing all the correct params and payload we are encountering issue.

    Below is the XSLT we used for Routing to backend.

                <xsl:variable name="sslprofile">

                      <xsl:value-of select="$RouteURI/RouteInfo/route/sslprofile[@name=$ruleName]/."/>

                </xsl:variable>

                <!-- sslprofile: setting the client profile by using the service variable -->

                <dp:set-variable name="'var://service/routing-url-sslprofile'" value="$sslprofile"/>

                <!-- routing url: setting the routing url by concating the URL and URI with the use of service variable -->

                <dp:set-variable name="'var://service/routing-url'" value="concat($OutBoundURL,$URI)"/>

                <xsl:copy-of select="."/>

                

    Error Response from DP:

    <?xml version='1.0' ?>

    <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>

        <env:Body>

            <env:Fault>

                <faultcode>env:Client</faultcode>

                <faultstring>Internal Error</faultstring>

            </env:Fault>

        </env:Body>

    </env:Envelope>

    Below are the logs wrote in DataPower Logs:

    6:38:17 PM  mpgw  error DEV-SIT     4694256     error 172.16.98.57      0x01130011  mpgw (MPGW-External-API-NONPROXY): Failed to process response headers

    6:38:17 PM  mpgw  error DEV-SIT     4694256           172.16.98.57      0x80e00126  mpgw (MPGW-External-API-NONPROXY): Valid backside connection cannot be established: Failed to process response headers, url: https://hostname/farmyieldreport/1.3/en

    6:38:17 PM  mpgw  error DEV-SIT     4694256           172.16.98.57      0x80e00626  mpgw (MPGW-External-API-NONPROXY): Error occurred when connecting to URL 'https://hostname/farmyieldreport/1.3/en'

    6:38:17 PM  mpgw  error DEV-SIT     4694256           172.16.98.57      0x80e0062a  mpgw (MPGW-External-API-NONPROXY): The header is empty when connecting to URL 'https://hostname/farmyieldreport/1.3/en'.

    If we use gatewayscript url-open we are getting below error in the same case:

    {

        "errorMessage": "The URL open() function cannot read the response from the stream. Error: Read from network stream timeout",

        "errorCode": "0x8580004e",

        "errorDescription": "The URL open() function cannot read the response from the stream",

        "errorSuggestion": "This error can be caused by an external entity (a remote server experiencing problems) or an internal issue. Check the log for additional messages on this same transaction for further clarification."

    }

    Any inputs will be helpful.



    ------------------------------
    Stefen Salvatore
    ------------------------------


  • 2.  RE: Failed to process response headers in MPGW

    Posted Tue August 27, 2024 11:08 AM

    So, other than the obvious information where DataPower is clearly mentioning it is unable to connect successfully to the back end server:

    Have you performed and analyzed a packet capture?

    What logs, if any, do you see from the server?

    Compare the SSL/TLS profile with that of the server (if there is a mismatch, it should be evident in the server logs).



    ------------------------------
    Joseph Morgan
    ------------------------------



  • 3.  RE: Failed to process response headers in MPGW

    Posted Tue August 27, 2024 11:43 AM

    Hi Attached the same.



    ------------------------------
    Stefen Salvatore
    ------------------------------

    Attachment(s)

    txt
    error-report (1).txt   25.21 MB 1 version
    zip
    capture (21).zip   345 KB 1 version


  • 4.  RE: Failed to process response headers in MPGW

    Posted Tue August 27, 2024 01:15 PM

    I'm seeing TLS 1.3 going to the server.  Is the server supporting TLS 1.3?



    ------------------------------
    Joseph Morgan
    ------------------------------



  • 5.  RE: Failed to process response headers in MPGW

    Posted Tue August 27, 2024 01:25 PM

    Sorry, I was looking at the wrong server.  Can you do another packet capture and filter on only the destination server.  I think the capture you attached is missing the failure.



    ------------------------------
    Joseph Morgan
    ------------------------------



  • 6.  RE: Failed to process response headers in MPGW

    Posted Wed August 28, 2024 07:38 AM
      |   view attached

    Hi Please find the attached pcap and the destination endpoint is https://extgw.nonprod.rbihub.io/farmyieldreport/1.3/en.



    ------------------------------
    Stefen Salvatore
    ------------------------------

    Attachment(s)

    zip
    capture (22).zip   406 KB 1 version


  • 7.  RE: Failed to process response headers in MPGW

    Posted Wed August 28, 2024 11:15 AM

    Is there, by chance, another proxy blocking the outbound requests.

    I can see certificates being delivered for "*.nonprod.rbihub.io", but then things fail after the new endpoint is set to ".../farmyieldreport/1.3/en".

    Also, what is the ip for your "extgw.nonprod.rbihub.io"?   The IP I'm getting on a nslookup is one not present in the packet capture. 



    ------------------------------
    Joseph Morgan
    ------------------------------



  • 8.  RE: Failed to process response headers in MPGW

    Posted Wed August 28, 2024 12:25 PM

    Had the same error :(



    ------------------------------
    Thomas Carpenter
    ------------------------------



  • 9.  RE: Failed to process response headers in MPGW

    Posted Wed August 28, 2024 01:46 PM

    Same endpoint, or similar breakdown of communications from DataPower to some other endpoint?



    ------------------------------
    Joseph Morgan
    ------------------------------