Hi Patrick,
It looks like that you don't have ipv6 support, maybe kernel module
don't loaded.
Try to test like this
$ ls /proc/net/if_inet6
Here is more info how to test ipv6 support in linux
http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/systemcheck-kernel.html
I clone you repository, apply you pat
I've put my sample code up on github, so we have something concrete to
talk about:
https://github.com/ppelleti/https-example
However, I think I've figured out why I'm getting the ECONNREFUSED: it's
for the obvious reason, that my server is only running on IPv4, and not
on IPv6. I was led ast
What about your ECONNREFUSED, does you have something like this, if
you run "curl -v --data CORRECT_POST_DATA_HERE HOST" ?
(it seems that you try POST request: client_do_post)
Does you server ("localhost") have the valid HTTP answer?
Why it couldn't get response after first request.
Could you post
On 01/22/2013 02:54 PM, Azat Khuzhin wrote:
Could you try to test my patch
https://github.com/azat/libevent/commit/71e709c7829275a594f767b27468b1b52e8b5bb9.patch
and write if it works for you?
Thanks, I think that's a step in the right direction.
However, I'm still having trouble. My callba
Hi Patrick, thanks, now understand that I don't see at the right peace of code.
Could you try to test my patch
https://github.com/azat/libevent/commit/71e709c7829275a594f767b27468b1b52e8b5bb9.patch
and write if it works for you?
Thanks.
On Tue, Jan 22, 2013 at 9:05 AM, Patrick Pelletier
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 matter. This is a general
problem with evhttp, regardless of OS.
Maybe
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:
>> On 11/19/201
On Sat, Jan 19, 2013 at 9:41 AM, Patrick Pelletier
wrote:
> On 11/19/2012 06:48 AM, Nick Mathewson wrote:
>
>> On Thu, Nov 15, 2012 at 2:32 AM, Patrick Pelletier
>> mailto:ppellet...@oblong.com>> wrote:
>> [...]
>>
>> Not sure what the proper solution is for this, though. I'm not
>> enoug
On 11/19/2012 06:48 AM, Nick Mathewson wrote:
On Thu, Nov 15, 2012 at 2:32 AM, Patrick Pelletier
mailto:ppellet...@oblong.com>> wrote:
[...]
Not sure what the proper solution is for this, though. I'm not
enough of a sockets expert. Although I'm curious why we need to
create the so
On Thu, Nov 15, 2012 at 2:32 AM, Patrick Pelletier wrote:
[...]
> Not sure what the proper solution is for this, though. I'm not enough of
> a sockets expert. Although I'm curious why we need to create the socket
> before we've looked up the name. If we looked up the name first, then we
> could
On 11/13/2012 09:48 PM, Patrick Pelletier wrote:
So, I figured out that the initial error that's occurring is
EAFNOSUPPORT. (Now, why that's happening is a separate mystery I need
to figure out... it happens when I use "localhost" as the hostname,
but not when I use "127.0.0.1".)
It looks li
On 11/01/2012 09:13 PM, Patrick Pelletier wrote:
Anyway, the error stack does seem to be empty, because
"ERR_print_errors_fp (stderr);" does not print anything. So, that
means I should look at errno, which is ENOTCONN.
So, I figured out that I shouldn't be looking at the OpenSSL error
stack,
12 matches
Mail list logo
