Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - HendersonS

#1
Web Services / Re: Unexpected Response in an HTTP Request
September 19, 2025, 04:41:59 PM
James we have checked it and we have not found any difference in the body, it even has exactly the same length except for the Boundary.
#2
Web Services / Re: Unexpected Response in an HTTP Request
September 19, 2025, 03:01:28 PM
Hi Devon, sorry for the delay in responding. We're trying to resolve this issue. We use byte counting, and the difference between the content length in Postman and pxplus is the Boundary length. Technically, this shouldn't affect the HTTP request, so we don't believe it's the issue. We're still trying to determine what the problem is. What do you suggest?
#3
Web Services / Re: Unexpected Response in an HTTP Request
September 09, 2025, 01:55:33 PM
Devon, we used the CALL "*tools/readfile",path$,xml_str$ tool to read the file, so I believe the length is correct.
#4
Web Services / Re: Unexpected Response in an HTTP Request
September 05, 2025, 09:54:10 PM
devon we saw those small differences but technically this should not have a negative impact on the http request, however we have made the changes so that it is exactly like in postman, except for the postman-token, the cookie and the content-length, which according to pxplus that would be the correct size (5506), I don't know why in postman it is a little smaller (5500), we are using pxplus 2025, but we have tried with several versions and we have the same results, the truth is we are running out of ideas, maybe we have to use powershell or c# to make the http request
#5
Web Services / Re: Unexpected Response in an HTTP Request
September 05, 2025, 01:53:27 PM
Thanks Devon for your reply, we tried that change but we have the same results, any other ideas?
#6
Web Services / Re: Unexpected Response in an HTTP Request
September 04, 2025, 08:51:48 PM
Thanks Loren for your reply. We saw that small difference and made the change, but we had the same results. We think it must be something with the headers, but we can't figure out what the error is.
#7
Web Services / Unexpected Response in an HTTP Request
September 04, 2025, 05:09:59 PM
Hello everyone, we are working with a third party API that we send xml files, and we are getting an unexpected response when we tried to post a file using the pxplus *plus/web/request utility, but when we use postman we get the expected response, we compare the raw http post, and initially we don't find any relevant differences.

this example of what we send from pxplus:
POST https://web.com/endpoint HTTP/1.1
Content-Type: multipart/form-data; boundary=----PxPlusFormDataBoundary_jqePihSICwS9OCggqvv6pcSWx53Sr4PI
Content-Length: 5506
User-Agent: CustomApp/3.5.1
accept-encoding: gzip, deflate, br
Accept: application/json
Authorization: bearer yJhbGciOiJIUzIfQ.VDMfa9MhV...
Host: web.com
Cache-Control: no-cache

------PxPlusFormDataBoundary_jqePihSICwS9OCggqvv6pcSWx53Sr4PI
Content-Disposition: form-data; name="xml"; filename="file_name.xml"
Content-Type: text/xml

<?xml version="1.0" encoding="utf-8"?>
<XMLCONTENT>
...HH
</XMLCONTENT>

------PxPlusFormDataBoundary_jqePihSICwS9OCggqvv6pcSWx53Sr4PI--

and this is the response:
HTTP/1.0 400 Bad Request
Content-Type: text/html

<html><head><title>Error</title></head><body>
<h2>ERROR: </h2>
<br>
</body></html>



this example from Postman:
POST https://web.com/endpoint HTTP/1.1
Authorization: Bearer yJhbGciOiJIUzIfQ.VDMfa9MhV...
User-Agent: PostmanRuntime/7.39.1
Accept: */*
Cache-Control: no-cache
Postman-Token: 84e36083-e8d2-45c0-a796-8ceba.......
Host: web.com
Accept-Encoding: gzip, deflate, br
Connection: keep-alive
Content-Type: multipart/form-data; boundary=--------------------------016854827228628556451404
Cookie: citrix_ns_id=AAI7XMG5aDvuodAGAAAAADtph5H_folAahaJO3ZgXF47eTRF6UPCLl86FZ_BO32DOw==Wci5aA==DQb-sHYMQEWeET5gyA37CgIG7zs=
Content-Length: 5500

----------------------------016854827228628556451404
Content-Disposition: form-data; name="xml"; filename="file_name.xml"
Content-Type: application/xml

<?xml version="1.0" encoding="utf-8"?>
<XMLCONTENT>
...HH
</XMLCONTENT>

----------------------------016854827228628556451404--

and the response is the expected json.

so What could be causing us not to have the same response in pxplus?

thanks in advance,
HendersonS.

#8
Hi Kevin, thank you very much. I see this is a great piece of work. I think it will be very useful. I'll try this repository and let you know what we think.
#9
Hi Kevin, we tried some prompts in Claude without much success, so maybe you could share those documents of the PxPlus manual conversions to Markdown files and others you mentioned so maybe we can replicate them and get better results. thanks in advance!

#10
Nomads / Re: Grid Images
May 15, 2025, 08:35:37 AM
Hi Jeffrey, can you post the solution you found?
#11
Thin Client/WindX / Re: Windx on a MAC
February 19, 2025, 01:54:55 PM
Hi,

Is it possible to run pxplus using Windows in parallels with the Apple M chip?

Regards,
HendersonS
#12
mike, I can Access without problems to: https://www.myserver.com/somefolder/restapi.pxp?route=/customers

The problem comes when I use AliasMatch and try to Access to: https://www.myserver.com/api/customers

I will continue investigating to see Apache permissions with directories

HendersonS
#13
Quote from: Mike King on December 17, 2024, 04:35:40 PMIf using Apache you can likely use AliasMatch or RedirectMatch to accomplish this.  Something like:

AliasMatch "^/api/(.*)" "/somefolder/restapi.pxp?route=/$1"

RedirectMatch would let you route to another server.

Using a generic match means you only need to setup one redirection/alias.

hi mike,

Have you tried this configuration? because I have tried it in every possible way and Apache always returns 403 forbidden, Maybe I'm doing something wrong but I don't know what it is, I mean I gave permissions to the directory, Alias works but AliasMatch doesn't.

Do you have any idea what might be wrong?

thanks in advance.
HendesonS
#14
Thanks Mike/Stéphane , I'm going to try that.
#15
Hello Stéphane,

I know this is a very old post, but can I ask you how you were able to make the rest api with pxplus, I mean, do you have to write every endpoint in the URL rewrite?

Thanks,
Henderson