> then used it everywhere
>
>
> to create the bug i connect frenzy to the server using a while true;
>
> Notice: if the program do not close the FD i exhaust the files desc before
> reaching the bug.
>
> --
>
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 Khuz
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
t;;, host: "localhost"
> ..
> nginx access.log:
> :::127.0.0.1 - - [11/Mar/2013:19:38:15 +0400] "POST /proxy/ HTTP/1.1" 200
> 13 "-" "-"
> ::ffff:127.0.0.1 - - [11/Mar/2013:19:38:22 +0400] "POST /proxy/ HTTP/1.1" 502
> 172 "-" "-"
> :::127.0.0.1 - - [11/Mar/2013
;
> bufferevent_free(bev);
> SSL_free(ssl);
>
> // this frees the stack of filters below "underlying"
> cleanup_ev_stack(underlying);
>
> // when this cb handler returns, all the bufferevents
> // have been freed
> }
> }
>
> Thank you
> Sasha
> ***
> To unsubscribe, send an e-mail to majord...@freehaven.net with
> unsubscribe libevent-users in the body.
--
Azat Khuzhin
ial
What about examples, you can see at libevent tests.
And also want to note that there is
git://github.com/ellzey/libevhtp.git - replacement for libevent's
httpd API.
On Sun, Jan 27, 2013 at 1:43 AM, Patrick Pelletier
wrote:
> Azat Khuzhin wrote:
>
>> It looks like that you don&#
getaddrinfo: address family for nodename not supported
> couldn't bind to port 8421. Exiting.
>
> So, I'm not sure what's going on there. And anyway, I don't really want to
> run the server on just IPv6; I want it to answer on both IPv4 and IPv6. But
> I don&
; read change was 0
> (none); write change was 1 (add): Bad file descriptor
>
> and my http request still fails. But that's as far as I've gotten in
> debugging it, though.
>
> But thanks for your patch! I think that will be part of the solution; I'm
> just running into other evhttp issues now (the ECONNREFUSED and retry
> thing).
>
> --Patrick
>
--
Azat Khuzhin
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
wrote:
> Azat Khuzhin wrote:
>>
>> Also on which operating system did you work?
>
>
> Ubuntu 10.04 LTS:
>
> Linux chives 2.6.32-34-generic #77-Ubuntu SMP Tue Sep 13 19:39:17 UTC 2011
> x86_64 GNU/Linux
>
> But the operating system doesn't really
Also on which operating system did you work?
Maybe this will be useful for you
http://instantbadger.blogspot.ru/2010/06/eafnosupport-socket-connection-issue-on.html
On Sun, Jan 20, 2013 at 7:18 PM, Azat Khuzhin wrote:
> On Sat, Jan 19, 2013 at 9:41 AM, Patrick Pelletier
> wrote:
>&
ess family we bound to. If we've bound to
>> 127.0.0.1, there's no point in doing an AF_UNSPEC name lookup -- we can
>> only connect to AF_INET addresses in that case.
>
>
> That's a potential workaround that would allow localhost (or any dual-stack
> host)
> 30 F0 1E 00 FF FF FF FF 00 00 00 00 00 00 00 00
> {477} normal block at 0x003E7F10, 24 bytes long.
> Data: <> F8 EF 1E 00 FF FF FF FF 00 00 00 00 00 00 00 00
> Object dump complete.
>
>
> 2012/12/4 Azat Khuzhin
>>
>> Hi,
>&g
12 matches
Mail list logo
