Hi Jack,

> It seems that HttpGetText does not support HTTPS?

Contrary to initial appearances, it not only supports https, but does it
very well. It's just that setting it up is just, well, non-obvious, and
requires an external SSL library (which is yet another benefit).

Note also that support for https is prominently mentioned on Synapse's
Features page http://synapse.ararat.cz/doku.php/features and elsewhere.
Looking in the source code, the documentation, the mailing list archives,
and in the Synapse cookbook should help a lot. Actually... it's the only way
to really use the library to any serious extent.

Here is Synapse's author's last answer to this issue, which obviously
happens more often:
http://sourceforge.net/mailarchive/message.php?msg_id=474D35BB.7850.2D9BF21D
%40gebylist.mlp.cz

- - - - -

For Lukas and the mailing list members at large:

I had been intending to discuss this and some related issues with Lukas, but
have been so busy the last few months that I haven't even been able to
download, install and use the latest version. (So I don't know what he's
changed already...)

Among the simpler suggestions was this: The previous person asking for help
with this issue reported  (in the above link) always getting http 500 error
codes (when trying to get https resources). This is obviously incorrect on
several levels, and I'm really surprised that no one brought it up, even
when it's been in the mailing list for months.

The THTTPSend.HTTPMethod function (in the httpsend unit) initializes the
FResultCode to 500 (to default to an error state), though that should ONLY
be reported *by the servers* we're querying when there's an "Internal Server
Error." So this is yet another misleading error coding. It would be far
better (assuming that we want to use only the one ResultCode property for
returning errors, even though it ostensibly exists for HTTP errors), to
choose an error code that is not currently defined as a real HTTP error
code; and it would probably be best to choose a code "far" away from the
currently defined ones.  Maybe something like 9999 ?  (4 digits, instead of
3, and numerically distant from the last used http error code...?)


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
synalist-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/synalist-public

Reply via email to