HTTPSecureSocket and PayPal Sandbox

PayPal recently started requiring HTTP/1.1 for testing applications in their sandbox. According to the Language Reference, HTTPSecureSocket uses HTTP/1.0, which now prevents me from doing sandbox testing on the PayPal system where it previously worked. Is there a way to force HTTPSecureSocket to use HTTP/1.1?

https://forum.xojo.com/10248-paypal-and-credit-card-payment-pack

read this

That is basically a discussion of the same problem I ran into. I was hoping that Xojo had a solution to the use of the deprecated HTTP/1.0 in HTTPSecureSocket.

I don’t think Xojo has HTTP/1.1 so I think we’re for now stuck with what I linked to.

Matthew Combatti has created a HTTP 1.1 Class that he sells.
Does not say anything about HTTPS though. Give him a bump. He’s on here somewhere :slight_smile:

http://www.xojodevspot.com/applications/easyshop/easyshop.php?prod.5

Matthew said the following if you follow the link I posted earlier

[quote=88170:@Albin Kiland]Matthew Combatti has created a HTTP 1.1 Class that he sells.
Does not say anything about HTTPS though. Give him a bump. He’s on here somewhere :slight_smile:

http://www.xojodevspot.com/applications/easyshop/easyshop.php?prod.5[/quote]

If you have the source, it shouldn’t be too difficult to port it to the secure socket. However, it’s a real pity Xojo doesn’t support 1.1.

It was scheduled over a year and a half ago. Hopefully it’s well underway and nearing release.

<https://xojo.com/issue/10311> Support HTTP 1.1

I’m not going to pay for a third-party solution to a Xojo problem that should be resolved by Xojo. The lack of support for HTTP/1.1 in web apps is going to be an increasing problem for Xojo web developers as more services phase it out.

[quote=88208:@Frederick Roller]It was scheduled over a year and a half ago. Hopefully it’s well underway and nearing release.

<https://xojo.com/issue/10311> Support HTTP 1.1[/quote]
That feedback case was opened on Nov 13, 2009 and the status merely shows that it’s “scheduled.” It does not appear to be a priority despite that fact that an increasing number of web services either already have or are planning to phase out HTTP/1.0.

I also have an Open Source PayPal payments solution at the site that is free :wink: If you need help getting it up and running in your web application…you can message me here or anywhere :slight_smile:

But try this…
http://xojodevspot.com/download.php?view.86

Usually, if you need something and can’t find it. I know exactly where to look…always a message away…

[quote=88381:@Matthew Combatti]I also have an Open Source PayPal payments solution at the site that is free :wink: If you need help getting it up and running in your web application…you can message me here or anywhere :slight_smile:

But try this…
http://xojodevspot.com/download.php?view.86

Usually, if you need something and can’t find it. I know exactly where to look…always a message away…[/quote]
I have a PayPal shopping cart that I created last year for use with ExpressCheckout payments that works quite well. The HTTP/1.0 problem that I ran into this week when trying to test an update in the PayPal sandbox is the only problem I’m having with it. It works on the live system which, fortunately, still accepts HTTP/1.0. I’m just a bit dismayed to run up against it now and discover that a feedback case has been open on the HTTP/1.1 issue for nearly five years with no action.

I did take a look at your PayPal solution and noticed that your PayPal class is also using HTTPSecureSocket, so it would have the same problem with the PayPal sandbox in that it no longer accepts HTTP/1.0 connections.