I don’t see anything in the documentation so this might be a dumb question: can the xojo.net.httpsocket be made secure like the HTTPSecureSocket?
It is by default. Give it a HTTPS URL and it’ll just do the right thing.
I find the documentation for the new framework to be…lacking…important details.
What about setting the socket to a specific port?
[quote=270867:@Bob Keeney] I find the documentation for the new framework to be…lacking…important details.
What about setting the socket to a specific port?[/quote]
Specify it in the URL.
All really important information for the documentation.
The docs say up top: “HTTPSocket handles both standard “http” connections and secure “https” connections.” which we thought was pretty clear. You have a suggestion to clarify? We’ll update as appropriate…
I do NOT see that in the Local documentation for R1.1.
Ah, OK. It’s since been updated online and is in the updated local r2 ref.
Maybe something like this?
HTTPSocket handles both standard “http” connections and secure “https” connections. Specify connection type and port within the url.
Example: https://somesite.com:8087 would attempt to make a secure “https” connection to “somesite.com” on port 8087.