Support for the use of HTTP version 1.1 protocol was added in PxPlus 2021 (v18.00).

If you are using an earlier version it is always using HTTP 1.0.

Is this still version 13.10?

If you open up that program on the system that gets the error is there a line 1875 and if so what is that code?

If there is no line 1875 you may have to open up a trace window and then cause the error to happen and then look through the trace.

Can you bypass your error handling to see if you can get the real line number?

Are you input field in a form?


There are several ways to have a web server interact with PxPlus for a overview check out this: https://home.pvxplus.com/files/7068/2024_v21_-_PxPlus_Web_Tools_Overview.pdf

Webster+ may be a good fir or *Web/Merge.

WindX SSH is handled via a included version of plink (putty command line).

It looks like putty got support for that cipher if the AI summary is to be believed in version 0.76. This is newer then your version of PxPlus so it explains the issue.

If you upgrade to the latest version of PxPlus it include plink 0.83 which would support the cipher.

TO find out what ciphers it does support you will have to look up putty documentation for the version of plink in your PxPlus install. It may or may not be possible to enable them on the server.

PxPlus does not come with any source analysis scanning tools. I am also not aware of any from a 3rd party that support scanning PxPlus code. Then again we have not looked into this ourselves and don't know much about what is available.

If you find a tool that ends up being useful please share here as it may be useful to others.

While not accessing variables like request you can use *BROWSER within pxplus to execute JS and get the return of a JS function call or define or set a JS global variable.

You will have to look at the documentation for the COM object method you are trying to execute. Maybe the arg list is different then you expect?

Here is the documentation for the *windx.utl program. AS Loren said you can use the *windx.utl;get_val to have the env() function run on the local/client machine.

https://manual.pvxplus.com?windx/windxutl.htm

Check the properties and methods available to pxplus by doing a

print EXP'*
or
print SIG'*

You can verify that Export() and SETX509CERT() are methods.

Other things to debug is check msg(-1) after you get the error for any more detailed error info. You could also checked

print EXP'PvxError$ for the same.

There is a property called SCALE=

It is mentioned in the documentation here: https://manual.pvxplus.com?directives/winprt_setup.htm

So if you want to set the property you could do something like

winprt_setup read properties P$
P$+="; SCALE=65"
winprt_setup write properties P$

This will read the current properties and add SCALE=65 where the 65 is 65%.

PRINT 'DIALOGUE'(0, 0, 60, 10, "Sample", 'WHITE' + '_BLUE', OPT="-mMSXZ")


This sets the foreground color to white and the background color to blue. You can replace 'WHITE' and 'BLUE' with any other valid color names as supported by PxPlus.

QuoteIf I have a +20 and -20, is that the *same* user slot.

Yes it means they are both using the same user slot. The +20 session acquired the user slot, the -20 session is using the user slot acquired by the first. This is because they are coming from the same client.

QuoteIf they initiate 2 sessions does this burn off one or 2 slots?

It should use up one user slot since it is the same client.

Running a WindX host/server does not require a Windows Server OS and can be run from Win 11 no problem.

in pxplus request Accept: application/json
in postman request Accept: */*

in postman there is a Connection: keep-alive which is not in pxplus request

In postman there is a cookie header that is not in pxplus

Beyond the body those are the differences it is got to be one of those or we are missing something.

The issue has been resolved. You should be able to call in now.