-
Alfredo Santibanez
- PowerBuilder
- Tuesday, 24 June 2025 01:45 PM UTC
Dear friends
I am moving my PB 12.6 applications to PB2025 solution and that process include moving the old Msxml2.XMLHTTP.6.0 oleobjects to call webservices with the new HTTP.
I have one case with problems that does not work with the new object but works with the old OLE, in the same function, with the same data., I would like to know if I am missing something in the Http call.
Original call is:
and so on, without the loggin process for simplicity
Results are:
2025/06/24 07:32:14 post https://data-api.globalforestwatch.org/dataset/umd_tree_cover_loss/latest/query
2025/06/24 07:32:15 send 200
2025/06/24 07:32:15 html {"data":[],"status":"success"}
With the HTTP
2025/06/24 07:29:25 st_code 307
2025/06/24 07:29:25 st_allheaders HTTP/1.1 307
Date: Tue, 24 Jun 2025 13:29:34 GMT
Via: 1.1 b26547db1e1891a614cdee548c1b3f08.cloudfront.net (CloudFront)
Content-Length: 0
Content-Type: application/json
Location: /dataset/umd_tree_cover_loss/v1.12/query
x-amzn-remapped-date: Tue, 24 Jun 2025 13:29:34 GMT
x-amzn-requestid: 27f92299-7821-4b35-9b3f-6a661aca4b61
x-amzn-remapped-content-length: 0
x-amzn-remapped-connection: keep-alive
x-amz-apigw-id: Mq852EJ9IAMEMgw=
x-amzn-remapped-server: uvicorn
x-cache: Miss from cloudfront
x-amz-cf-pop: MIA3-C3
x-amz-cf-id: 4J6gWpNh70XAKujB5Ox_st5AdpfF2MvM2Sqzo4mI5VVExo9dpDj_hw==
2025/06/24 07:29:25 post response https://data-api.globalforestwatch.org/dataset/umd_tree_cover_loss/latest/query
2025/06/24 07:29:25
No response body
As I said before, the url, authentication and body are the same.
Any similar case that you know or a workaround like a missing header not in the defaults?
Best Regards
Alfredo
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.