Trying to call a REST service from within Uniface code. 

Using the following code. 

			putitem/id v_headers,"X-PCI-Token",<token>
			putitem/id v_headers,"content-type","application/json"
			v_data = $newstruct
			.... some code to build the struct correctly....... 
			structtojson/whitespace  v_content, v_data
			$api$->set_flags(15)
			v_status = $api$->SEND($uri$, "POST", "", "", v_Headers, v_Content, v_Response)

v_headers, v_contact and v_response are all strings. 

I have checked v_content just before the send operation, and it contains correctly formatted JSON. Pasting this JSON into SoapUI activates the far end correctly. 

However, logging on the far end shows blank content when send from uniface. 

Is there any way I can catch/log the output of UHTTP to get the raw data sent to the far end? Or can anyone spot why UHTTP might be clearing the content before sending (bad parsing or something?

Iain

JSON content sample for reference. 

 { 
  "subscription_type" : "company.creation",
  "properties" : { 
   "name" : "St, Vat, Eom, No stdisc. Doc Email",
   "phone" : "+44114201220",
   "address_line_1" : "23 PCI House ims",
   "address_line_2" : "Woodseats Avenue",
   "city" : "Sheffield",
   "county" : "S. Yorkshire",
   "country" : "UK",
   "post_code" : "S8 0TB",
   "company_tier" : ""
 }
}

$api$->set_flags(15)
this includes
4  = Do not calculate the content-length of the payload itself for a POST method.

Have you tried set_flags(11).
I usually use set_flags(10) or set_flags(8). But that depends on your environment.

Trying to call a REST service from within Uniface code. 

Using the following code. 

			putitem/id v_headers,"X-PCI-Token",<token>
			putitem/id v_headers,"content-type","application/json"
			v_data = $newstruct
			.... some code to build the struct correctly....... 
			structtojson/whitespace  v_content, v_data
			$api$->set_flags(15)
			v_status = $api$->SEND($uri$, "POST", "", "", v_Headers, v_Content, v_Response)

v_headers, v_contact and v_response are all strings. 

I have checked v_content just before the send operation, and it contains correctly formatted JSON. Pasting this JSON into SoapUI activates the far end correctly. 

However, logging on the far end shows blank content when send from uniface. 

Is there any way I can catch/log the output of UHTTP to get the raw data sent to the far end? Or can anyone spot why UHTTP might be clearing the content before sending (bad parsing or something?

Iain

JSON content sample for reference. 

 { 
  "subscription_type" : "company.creation",
  "properties" : { 
   "name" : "St, Vat, Eom, No stdisc. Doc Email",
   "phone" : "+44114201220",
   "address_line_1" : "23 PCI House ims",
   "address_line_2" : "Woodseats Avenue",
   "city" : "Sheffield",
   "county" : "S. Yorkshire",
   "country" : "UK",
   "post_code" : "S8 0TB",
   "company_tier" : ""
 }
}

And you don't have problems with whitespaces?
Have you tried leaving out  /whitespace in structtojson?

You could add the following to your ASN and check the resulting tracing of the UHTTP component:

[SETTINGS]
$trc_levels=9U
$trc_info=num,cat,lvl
$trc_start=uhttp.trc

This should show you what the content is that is send. E.g.

2;   10U;uhttp> uhttp_send> contents={"authorization_id":"ABC123","..., size=239

If I, however, really want to be sure what is going over the line then I usually use a web debugging tool (like e.g. Fiddler) or a network packet analyzer (like e.g. WireShark).

I hope this helps.

I will try this and see if it shows me the necessary. 

Attached are the two outputs with flags set to 10 and 15. One (flags at 15) results in blank contents logged at the other end, the other (10) results in a 502 error from the other end, and I have not yet had feedback as to what is logged. 
Servername changed to protect the (not so) innocent. 

It seems that the request is forwarded from:

http://apiserver/webhooks/pci.php

To:

https://apiserver/webhooks/pci.php

I do not think that the content should change when the request is repeated to the new URL. Did you already try if it makes a difference when you call the https URL directly?

It seems that the request is forwarded from:

http://apiserver/webhooks/pci.php

To:

https://apiserver/webhooks/pci.php

I do not think that the content should change when the request is repeated to the new URL. Did you already try if it makes a difference when you call the https URL directly?

Ding, ding. ding. ding! we have a Winner!

I tried the flags at 26 to catch the redirect, and then changed it to call the https: site directly. This worked. I will look at fixing it to catch a new server and repeat loop call resetting the contents. 

I would not expect it to wipe the contents on a redirect though? It seems it does though. 

Regards, 

Iain