Hello [EMAIL PROTECTED]
In the past, when I was developing a connection to one HTTPS server of
big institution using by Indy, I was getting "Connection Closed
Gracefully." and I spent long time to find out why. I tried it with
WinInet and the connection was OK. Afterwards I found, that that
server doesn't act as it should
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.23
and I needed to add into Indy's http component property which prevent
of port number sending in HTTP header.
Actually I am working on porting into Synapse and of course I have the
same problem. I have added the same thing into Synapse, but maybe it
would be fine to have this property in Synapse by default.
What do you (?Lukas?) think about it?
Please don't beat me, that it is unusual, but I don't have any
possibility to change the behavior of that server and maybe this
happens in more cases.
My changes in httpsend.pas:
THTTPSend = class(TSynaClient)
protected
...
FRangeEnd: integer;
FAddPortNumberToHost: Boolean; // rt 9.5.2007
published
property Sock: TTCPBlockSocket read FSock;
{:To have possibility to switch off port number in HTTP's header, by
default TRUE.}
property AddPortNumberToHost: Boolean read FAddPortNumberToHost write
FAddPortNumberToHost; // rt 9.5.2007
constructor THTTPSend.Create;
begin
...
FUploadSize := 0;
FAddPortNumberToHost := TRUE; // rt 9.5.2007
function THTTPSend.HTTPMethod(const Method, URL: string): Boolean;
...
if (Port<>'80') AND FAddPortNumberToHost then // rt 9.5.2007
--
Best regards, TRoland
http://www.rotursoft.sk
http://exekutor.rotursoft.sk
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
synalist-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/synalist-public
