|
This more a post of observations we have following successfully deploying the SQLA webclient to communicate with a third party webserver as most of the information we found was out of date: 1) Sybase 17.0.11 on Windows uses the operating systems certificate store, provided the server is using a public CA there is no need to declare the certificate in the Procedure. 2) Remember to set "type ' 3) Set the header " 4) You probably want to ensure you use " 5) set option The above has certainly given us a rock solid https client which communicates with third parties nicely. |
|
Just to add: To understand and check requests and responses, particularly for newly embedded web services, we usually have to turn on "Web client logging debugging" temporarily, as described here. FWIW, the usage of this feature via "dbsrvX -zoc MyWebClientLog.txt" or call sa_server_option('WebClientLogFile', 'MyWebClientLog.txt');
call sa_server_option('WebClientLogging', 'On');
has not changed for newer versions.
Yes, this was also useful.
(05 May, 06:41)
pcollins
|
Are you sure on that? According to the 17.0.1. docs type is restricted to HTTP (or SOAP). We do use HTTP but provide an URL with https: for secure connections.
Great suggestions, anyway! FWIW, we have not needed to increase the default remote_idle_timeout value, probably as most web services are hosted locally.
Yes, this tripped us up for awhile and we were getting inconsistent connections but if you read the examples on that page it shows using HTTPS:POST in a couple of the examples so we tried it and haven't reverted back.
The timeout issue is very much dependent on the servers, we didn't come across it as a problem when testing locally for sure and it really depends on the load of the server, some third parties servers don't get impacted, same again with
"Connection:keep-alive"Yes, I asked on the doc page for further clarification between the syntax description and the samples... (The 17.0.0 docs do have TYPE 'HTTPS:POST...' in their samples, too.)