Thanks, Lucas.
So, instead of using HttpPostUrl, I would just have to write my own little
HttpPostUrl, so that I can set http.protocol and keepalive, right?
Best regards,
- Klaus -
----- Original Message -----
From: "Lukas Gebauer" <gebyl...@mlp.cz>
To: "Ararat Synapse" <synalist-public@lists.sourceforge.net>
Sent: Tuesday, October 02, 2012 4:54 PM
Subject: Re: [Synalist] Basic Question about HTTP 1.1 in Synapse httpsend
> > I am using HttpPostURL to communicate with Paypal. Paypal will soon
> > require certain requests ("IPN") to be sent with HTTP 1.1 and to
> > contain "Host: http://www.paypal.com"; and "Connection: close" in the
> > HTTP header.
> >
> > I guess it will not be sufficient to just set
> >
> > FProtocol := '1.1';
> >
> > in constructor THTTPSend.Create ?
>
> Why not use properties?
>
> http := THttpSend.create;
> http.protocol := '1.1';
> http.keepalive := false;
>
> Your requested headers are created internally by Synapse, this
> settings create headers as you need.
>
> Just "Host" header is created without protocol portion, just "Host:
> www.paypal.com", because it say RFC2616.
>
>
>
> --
> Lukas Gebauer.
>
> http://synapse.ararat.cz/ - Ararat Synapse - TCP/IP Lib.
> http://geoget.ararat.cz/ - Geocaching solution
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
synalist-public mailing list
synalist-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synalist-public
