Very strange behavior

General
1

Hi Node-Reders,
I have a very strange thing happening. I am sending a post request to an api endpoint.
there are number of nodes that I coded the logic but at the end I am sending below msg to the http request node.

{
   "symbol":"THYAO",
   "direction":"BUY",
   "lot":1,
   "payload":"{\"symbol\":\"THYAO\",\"direction\":\"BUY\",\"pricetype\":\"piyasa\",\"price\":\"\",\"lot\":\"1\",\"sms\":true,\"email\":false,\"subAccount\":\"\"}",
   "headers":{
      "Content-Type":"application/json; charset=utf-8",
      "APIKEY":"API-fEceFLSYQFLvI5h5MeSnNxJ4V5B3pE8YucJvyRfxFw",
      "Authorization":"eyJhbGciOiJodHRwOi8vd3d3LnczLm9yZy8yMDAxLzA0L3htbGRzaWctbW9yZSNobWFjLXNoYTI1NiIsInR5cCI6IkpXVCJ9.eyJBdXRob3JpemF0aW9uIjoiQXV0aG9yaXplZCIsIkN1c3RvbWVyTm8iOiIyMDgwOTE2OCIsIk5ld3NsZXR0ZXIiOiJUcnVlIiwiSXNCbG9ja2VkIjoiRmFsc2UiLCJFbWFpbCI6Im5lcmdpbmVyQGdtYWlsLmNvbSIsIlVzZXJJZCI6IjQwMTMiLCJEZW5pemJhbmsiOiJUcnVlIiwibmJmIjoxNjc1MDY4NzczLCJleHAiOjE2NzUxNTUxNzN9.IcVLbSc9EAshmBXS79uXaiaYbCTGDHSgtv_QHX3XqYc",
      "Checker":"da17aa13bc48f043deddafd35f60e8801fa9f40025d74e5e2a109a6160a1148e"
   },
   "_msgid":"1124136dca420cf7"
}

It response back with this error message.

<html>
  <head>
    <title>Request Rejected</title>
  </head>
  <body>The requested URL was rejected. Please consult with your administrator. <br>
    <br>Your support ID is: 12854212357508180978 <br>
    <br>
    <a href='javascript:history.back();'>[Go Back]</a>
  </body>
</html>

But If I insert an inject node before the http request and insert the data on the inject node it works. Please find the debug out come of the inject node.

{
   "symbol":"THYAO",
   "direction":"BUY",
   "lot":1,
   "payload":"{\"symbol\":\"THYAO\",\"direction\":\"BUY\",\"pricetype\":\"piyasa\",\"price\":\"\",\"lot\":\"1\",\"sms\":true,\"email\":false,\"subAccount\":\"\"}",
   "headers":{
      "Content-Type":"application/json; charset=utf-8",
      "APIKEY":"API-fEceFLSYQFLvI5h5MeSnNxJ4V5B3pE8YucJvyRfxFw",
      "Authorization":"eyJhbGciOiJodHRwOi8vd3d3LnczLm9yZy8yMDAxLzA0L3htbGRzaWctbW9yZSNobWFjLXNoYTI1NiIsInR5cCI6IkpXVCJ9.eyJBdXRob3JpemF0aW9uIjoiQXV0aG9yaXplZCIsIkN1c3RvbWVyTm8iOiIyMDgwOTE2OCIsIk5ld3NsZXR0ZXIiOiJUcnVlIiwiSXNCbG9ja2VkIjoiRmFsc2UiLCJFbWFpbCI6Im5lcmdpbmVyQGdtYWlsLmNvbSIsIlVzZXJJZCI6IjQwMTMiLCJEZW5pemJhbmsiOiJUcnVlIiwibmJmIjoxNjc1MDY4NzczLCJleHAiOjE2NzUxNTUxNzN9.IcVLbSc9EAshmBXS79uXaiaYbCTGDHSgtv_QHX3XqYc",
      "Checker":"da17aa13bc48f043deddafd35f60e8801fa9f40025d74e5e2a109a6160a1148e"
   },
   "_msgid":"39b6baeb0821bbdd"
}

I text compare the data and only the _msgid is different.
I select the complete object output from the debug node.

What is the difference can be that cause the api end point returns with error in one massage but ok with the other. Do msg object have some hidden properties that I can not output?
Any idea is welcome.

PS:
The apikey is fake

Regards,
Nuri

3

changing return as below also do not solve.

return {
    "payload":msg.payload,
    "headers":msg.headers
};

So this is not related with the msg object. But what can be the reason of error so strange.
Please help!

4

I find out that I am making two requests very rapidly. I put a delay and it solve the issue.
Sorry for disturbing

5

IF that is your real API key you may wish to edit/delete/change it...

6

As I mentioned in the post I fake the APIKEY it is not real.
Thanks for the warning

7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.