Hi,

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

Regards,
HendersonS

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

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

Thanks Mike/Stéphane , I'm going to try that.

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

Hi everyone, is there a way to download a copy of the demo that is at https://demosite.pvxplus.com/?

Hi,
Jeff and Stéphane, thank you for your help, I was finally able to find the solution with the help you gave me.

the line looked like this:
Content-Disposition: form-data; name="xml"; filename="xmlsing.xml"

jeff,

I tested both ways that you showed me and I still get the same "invalid file" response, I will continue trying...

jeff, this is what it returns:

1>print mid(body$,1,300)
------PxPlusFormDataBoundary_zNYKbtQdhRIYGlYIDBoKNPAdi7un9gGR
Content-Disposition: form-data; name="xmlsing"; filename="xmlsing.xml"
Content-Type: text/xml

<?xml version="1.0" encoding="utf-8"?>
<SemillaModel xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="h
ttp://www.w3.
1>

Jeff thanks for your help,

I have something very similar to what you showed, I also added Stephane's program to calculate the boundaries but when I send it with pxplus the API returns an "invalid file" error, I tried it with CURL and the api receives the file correctly, does it work? How could I replicate it? in Pxplus?

Example with CURL: curl -X 'POST' \
  'https://url/api' \
  -H 'accept: application/json' \
  -H 'Content-Type: multipart/form-data' \
  -F 'xml=@xmldata.xml;type=text/xml'


Hi Jeff, I'm stuck in the same place trying to send a file via API, could you post the final solution? Maybe it can help me too!

Jeffrey Ferreira,
I'm working on something similar, how did you create the boundary?

Loren, thanks for your demonstration,

so far I have not been able to install xmlsec on Windows, and I have not been able to find a solution with pxplus either, so I will have to make some program in C# or another language to invoke it from pxplus, since I do not see a solution with pxplus.

Thanks Mike for your instructions.

If I understood correctly, you mean that I can invoke this tool from pxplus? And just in case I take another route to do it with pxplus, is there any utility to extract the private key from a .pem?

Loren thanks for yor reply

Below is the structure that the signature node should have within the xml, I have no experience in building these signatures. Maybe you can show me some example code to do it.

<Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
<SignedInfo>
<CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/RECxml-c14n-20010315" />
<SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsigmore#rsa-sha256" />
<Reference URI="">
<Transforms>
<Transform Algorithm="http://www.w3.org/2000/09/xmldsig#envelope d-signature" />
</Transforms>
<DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256" />
<DigestValue>Atr9H7DiGlxrQOFII/hFihsL6ACiwe47Oo93tgtuera=</DigestValue>
</Reference>
</SignedInfo>
<SignatureValue>gQyXO0FFDGIITESTpP5xZjLIRtv/Q7/ixe1lNDLDA5aw...</SignatureValue>
<KeyInfo>
<X509Data>
<X509Certificate>DGIITESTBFagAwIBAgIIInYGQUX9q0IwDQYJKoZIhvcNAQ...</X509Certificate>
</X509Data>
</KeyInfo>
</Signature>