New framework: HTTPSocket is not yet compatible with Web Apps

Oliver_Osswald · October 1, 2015, 12:15pm

In the documentation it says:

http://developer.xojo.com/xojo-net-httpsocket

Also, for the security settings it says:

http://developer.xojo.com/xojo-net-sslsettings

So, this is correct, at the moment we cannot replace httpsecuresocket in a web application, right?

Greg_O_Lone · October 1, 2015, 1:00pm

Right, and being that web apps are just a Service Application under the hood, I’d expect them to have this problem too (and by extension, Console Applications).

Tim_Parnell · January 23, 2016, 10:09pm

Considering PayPal will require HTTP 1.1, HTTPS, and TLS 1.2 at the end of September is there any status update on this? I’d like to be able to handle payment notifications.

Michel_Bujardet · January 23, 2016, 10:45pm

To be more precise, Paypal IPN has been requiring HTTP1.1 since Feb 2013.

At this moment I use a PHP listener, which calls a Xojo app for the generation of license information when needed.

It sure would make sense to have that Xojo app listen to instant payment notification itself.

I am somewhat disillusioned right now…

Tim_Parnell · January 23, 2016, 11:22pm

Without being able to connect to PayPal with HTTP1.1 and SSL, Xojo Web Apps are left totally useless for payment verification. I’m sure developers would appreciate PayPal IPN capabilities in Xojo instead of workarounds with PHP.

Michel_Bujardet · January 23, 2016, 11:30pm

It would go a long way for Xojo recognition to have a Xojo listener example in the list of languages available on https://github.com/paypal/ipn-code-samples

Tim_Parnell · January 23, 2016, 11:45pm

My plan was to make a control that could handle the IPN as I’m sure there’s people here interested in buying it.

But either way, Xojo cannot connect to PayPal until the security settings and net.socket are available for Web.

Eric_Wilson · February 12, 2016, 4:14am

As of today (12 Feb 2016) can we use Paypal with Xojo or not?

It seems the HTTPS requiremet for Paypal IPN will only be enforced in September, or do they require it today for new customers?

Tim_Parnell · February 12, 2016, 4:26am

They require http 1.1 as of right now, so no.

Eric_Wilson · February 12, 2016, 4:40am

Wow.

Christian_Schmitz · February 12, 2016, 7:38am

You can use MBS CURL Plugin.
Does TLS 1.2, HTTP 1.1 and HTTPS with local certificates.

http://www.monkeybreadsoftware.de/xojo/plugin-curl.shtml

Eric_Wilson · February 13, 2016, 12:36pm

Thanks Christian, I will check it out.

Also, if one happens to be in Australia, Australia Post’s Secure Frame all-in-one gateway/merchant account also seems compatible.
https://www.securepay.com.au/developers/products-and-services/accepting-e-commerce-payments/secureframe

Michel_Bujardet · February 13, 2016, 1:54pm

Actually, the way the Paypal IPN listener is built in Php or Perl is rather simple.

Paypal hits the listener with a Post containing all the fields, and the app replies by posting back the values with a token added. In Php when they started requiring 1.1 it was just a matter of one header to add.

https://developer.paypal.com/webapps/developer/docs/classic/ipn/integration-guide/IPNImplementation/

I cannot remember at the moment if and which headers if any HandleURL and HandleSpecialURL send, but it would not seem terribly difficult to do exactly the same. In this instance, I do not think Xojo.Net.HTTPSocket would be of any help, since it does not listen anyway.

Using the API is another matter, but in that case the MBS CURL plugin probably has that covered.