ire.
Bottomline:
Did I initially use it wrongly? If so, please state in the docs that I
should have included the '\0'. Did I stumble upon an error?
regards,
Oscar Koeroo
smime.p7s
Description: S/MIME Cryptographic Signature
On 19/8/11 1:14 PM, Leonid Evdokimov wrote:
> Hello,
>
> Here is patch to add "host" header to outgoing HTTP/1.1 requests.
> Please, review.
>
> Without the patch libevent-based evhttp-client.c can't get reply from
> any sane server because the request is rejected with "400 Bad request"
> and wor
epend upon OpenSSL heavily, hence my inquiry about
the matter. We also extend OpenSSL in some places and for our specific use
cases.
regards,
Oscar Koeroo
Nikhef
smime.p7s
Description: S/MIME Cryptographic Signature
Hi Amarin,
Could you checkout the "0.4.5" tag of libevhtp and rebuild with that one? I
don't think master is the right starting point.
I tried your code and my Chrome (version 18.x devel), Firefox 9.0.1 and
Opera 11.60 worked fine.
I've statically build your code against libevent release-2.0.16-
-rest/blob/master/src/lcmapsd_httprest.c
Oscar
On 13/1/12 9:20 PM, Oscar Koeroo wrote:
> Hi Amarin,
>
> Could you checkout the "0.4.5" tag of libevhtp and rebuild with that one? I
> don't think master is the right starting point.
>
> I tried your code
On 10-12-12 08:36, Nick Mathewson wrote:
> On Sat, Dec 8, 2012 at 6:03 AM, Patrick Pelletier
> wrote:
>
>> However, it's not clear to me how to work the validation function
>> (validate_hostname) into evhttp's control flow. It seems that I would need
>> to call validate_hostname after the TLS h
On 18-01-13 04:26, Patrick Pelletier wrote:
> On 12/10/2012 03:05 AM, Patrick Pelletier wrote:
>
>> So I had been thinking it couldn't be done with the callback. However,
>> after re-reading the manpage for SSL_CTX_set_verify, it sounds like it
>> does get called on success, and is given the oppo
On 11-03-13 16:00, Alexey Ozeritsky wrote:
> libevent does something wrong:
>
> $ ./sample/https-client -url https://localhost/proxy -data 4K -ignore-cert
> Response line: 200 OK
> OK
>
> $ ./sample/https-client -url https://localhost/proxy -data 512K -ignore-cert
> Response line: 502 Bad Gateway