Layer7 API Management

Expand all | Collapse all

Getting Invalid URI - 601 error. Can someone help on this?

Jump to Best Answer
  • 1.  Getting Invalid URI - 601 error. Can someone help on this?

    Posted 05-24-2017 11:56 PM

    Hi Team,

     

    I am getting an Invalid URI (601) error while trying to hit the request from IE browser. The same request If I try from Google chrome, it has processed successfully. May I know why this is happening? Is it possible to resolve this issue?

     

    Error msg: Invalid URI

    http://<<host>>:<<post>>/invoke/Loyalty.interfaces.Inbound.webServices.caltex:webSrvRedemptionRequest_1?xmlRequest=<?xml%20version="1.0"?><RedemptionRequest><Header><RequestorTrxTime>2017-05-23%2014:58:30</RequestorTrxTime><RequestorContext>22128-01</RequestorContext><TrxNumber>0143</TrxNumber><LoyaltyNumber>9344668231712</LoyaltyNumber><UserId>svc_TUR_ST</UserId><Password>caltex123</Password><MessageExpiry>5000</MessageExpiry></Header>



  • 2.  Re: Getting Invalid URI - 601 error. Can someone help on this?

    Posted 05-25-2017 10:00 AM

    A 601 error can be caused by many things, but generally means an "Error in Assertion Processing", as documented here:

    Assertion Status Codes - CA API Gateway - 9.2 - CA Technologies Documentation 

    Does the audit log on the gateway give you an indication as to what the assertion error is causing this 601 response?



  • 3.  Re: Getting Invalid URI - 601 error. Can someone help on this?
    Best Answer

    Posted 05-25-2017 07:11 PM

    Hello ppadmanaban.1 ,

    You need to url encode the parameter value.

    If there is a client app,  it's done before it sends the request. If you just input url in a browser, you can find an online url encode website (such as URL Encode Decode - URL Percent Encoding and Decoding.), to encode the xml document, and put the encoded string to xmlRequest parameter, it looks like,

    http://<<host>>:<<post>>/invoke/Loyalty.interfaces.Inbound.webServices.caltex:webSrvRedemptionRequest_1?xmlRequest=<url encoded xml>

     

    Regards,

    Mark



  • 4.  Re: Getting Invalid URI - 601 error. Can someone help on this?

    Posted 05-25-2017 09:58 PM

    Hi Zhijun He,

     

    Is it possible to encode the xml in our gateway?



  • 5.  Re: Getting Invalid URI - 601 error. Can someone help on this?

    Posted 05-28-2017 07:28 PM

    Surely you can, you can use Encode/Decode data assertion, and select URL encode, for more details, please refer to,

    Encode/Decode Data Assertion - CA API Gateway - 9.2 - CA Technologies Documentation 



  • 6.  Re: Getting Invalid URI - 601 error. Can someone help on this?

    Posted 05-28-2017 09:24 PM

    No luck with Encode/Decode data assertion. I just set the variables like below. But still getting the same error.

    Source Variable : ${request.url}

    Target Variable : ${url}



  • 7.  Re: Getting Invalid URI - 601 error. Can someone help on this?

    Posted 05-29-2017 06:44 PM

    Hello ppadmanaban.1,

    It looks like you're trying to encode the incoming request, it won't work.

    The encoding needs to be done on client  side. You use the encode assertion only if the gateway is the client and the gateway compose a request and send it to backend.

     

    Furthermore, you should not encode the whole url, only need to encode the parameter value.

     

    Regards,

    Mark