App Connect

 View Only
Expand all | Collapse all

HTTPRequestIdentifier generation logic - for HTTP solution

  • 1.  HTTPRequestIdentifier generation logic - for HTTP solution

    Posted Wed September 21, 2022 10:11 AM
    Dear All,

       Part of HTTP sync solution Using HTTPRequestIdentifier considering it always starts with 4556 series, we have seen the same in multiple systems and operating systems.

    IF StARTSWITH(InputLocalEnvironment.HttpRequestIdentifier, '4556') THEN 

      Statements ,

    END IF;

    Can we write that logic, or HttpRequestIdentifier will change, if yes what could the generation logic. 

    Quick response much appreciated.


    Regards,

    ------------------------------
    gurudatha n
    ------------------------------


  • 2.  RE: HTTPRequestIdentifier generation logic - for HTTP solution

    Posted Wed September 28, 2022 01:33 PM
    The HTTP identifier used by the HTTP nodes in ACE is not a static value.  It increments over time.  There is no certainty that the 4556 part will always be there.  The generation logic is not documented and subject to change at any time.  It is not a good idea to create such an IF statement as you have no control over what the value will be and thus the IF will return true/false potentially randomly.
    What are you trying to accomplish with this?  Perhaps an HTTP header or something in the message body would be a better option.

    ------------------------------
    MATTHEW SEGALL
    ------------------------------

    Original Message