Hello,
I've added support of POST requests to sample/https-client.c:
https://github.com/resetius/libevent/commit/c5887f73b707a7e95b986a0c5eede80ef7741d09
This is useful to reproduce the bug
http://sourceforge.net/tracker/index.php?func=detail&aid=3526934&group_id=50884&atid=461322
$ ls -l *K *M
11.03.2013, 19:31, "Oscar Koeroo" :
> 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 -dat
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
With my libevent version 512KiB transmitted succesfully.
azat:.../libevent/sample (https)$ tr -dc A-Za-z0-9 | ../../data.512.kb
azat:.../libevent/sample (https)$ ./https-client -url
https://127.0.0.1/proxy -data ../../data.512.kb -ignore-cert
Response line: 200 OK
OK
But 4MiB:
azat:.../libevent/s
On Mon, Mar 11, 2013 at 11:22 PM, Azat Khuzhin wrote:
> With my libevent version 512KiB transmitted succesfully.
>
> azat:.../libevent/sample (https)$ tr -dc A-Za-z0-9 head -c$((512 * 1024) >| ../../data.512.kb
> azat:.../libevent/sample (https)$ ./https-client -url
> https://127.0.0.1/proxy -dat
Also I want to note that HTTP POST works fine with 100 MiB.
I added test to test/regress_http.c.
Nick do you think that it is need for libevent upstream?
Which I can not say about HTTPS.
On Mon, Mar 11, 2013 at 11:26 PM, Azat Khuzhin wrote:
> On Mon, Mar 11, 2013 at 11:22 PM, Azat Khuzhin wrote