<div dir="ltr">Hi<div>I have to note that I did do the testing with a partner at a different physical location. My Linux laptop with FF and Chrome did not cause a crash, his Chrome/FF and IE caused the crash. I will retest with him today and let you know results. What is better to use in terms of speed zlib or xcodec ?</div>
<div>Regards<br><br><div class="gmail_quote">On Mon, Dec 19, 2011 at 4:12 AM, Juli Mallett <span dir="ltr"><<a href="mailto:juli@clockworksquid.com">juli@clockworksquid.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Neither of those errors is necessarily bad. A lot of connections get<br>
closed that way. The thing about the deflate stream not ending neatly<br>
is also not uncommon. Were you able to access websites with that<br>
configuration? It's the crash that you saw earlier that concerns me<br>
as long as everything else is working alright.<br>
<div class="HOEnZb"><div class="h5"><br>
On Sun, Dec 18, 2011 at 15:38, Ali Jawad <<a href="mailto:alijawad1@gmail.com">alijawad1@gmail.com</a>> wrote:<br>
> Hi<br>
> My initial settings are same as the<br>
><br>
> Proxying over a WAN using SOCKS<br>
><br>
> Example, in this example Zlib is not enabled and I get the error mentioned<br>
> in the last emails, upon disabling xcodec and enabling zlib as in the config<br>
> example "only relevant top part" I get this error :<br>
><br>
><br>
> Server<br>
><br>
> create codec codec0<br>
> #set codec0.codec XCodec<br>
> #activate codec0<br>
><br>
> set codec0.compressor zlib<br>
> set codec0.compressor_level 6<br>
> activate codec0<br>
><br>
><br>
> Client<br>
><br>
> create codec codec0<br>
> #set codec0.codec XCodec<br>
> #activate codec0<br>
><br>
> set codec0.compressor zlib<br>
> set codec0.compressor_level 6<br>
> activate codec0<br>
><br>
><br>
> I get this error :<br>
> 1324250995.222191 [/wanproxy/proxy/proxy0/connector] ERR: void<br>
> ProxyConnector::splice_complete(Event): Unexpected event: <Error>/104<br>
> [Connection reset by peer]<br>
> 1324250995.222342 [/zlib/deflate_pipe] ERR: virtual<br>
> DeflatePipe::~DeflatePipe(): Deflate stream did not end cleanly.<br>
><br>
> When I commented out the activate codec line using the same config copied<br>
> above I got this error :<br>
><br>
> 1324251200.589366 [/wanproxy/proxy/proxy0/connector] ERR: void<br>
> ProxyConnector::splice_complete(Event): Unexpected event: <Error>/104<br>
> [Connection reset by peer]<br>
><br>
><br>
><br>
><br>
> On Mon, Dec 19, 2011 at 1:38 AM, Ali Jawad <<a href="mailto:alijawad1@gmail.com">alijawad1@gmail.com</a>> wrote:<br>
>><br>
>> Hi<br>
>> Did svn up to 897 ..did make clean and called make, will update with<br>
>> results, if I get errors will disable zlib and report back as well.<br>
>> Regards<br>
>><br>
>><br>
>> On Mon, Dec 19, 2011 at 1:34 AM, Juli Mallett <<a href="mailto:juli@clockworksquid.com">juli@clockworksquid.com</a>><br>
>> wrote:<br>
>>><br>
>>> I meant the binary on both the client and the server.<br>
>>><br>
>>> To disable zlib, just comment out or remove the lines like these in<br>
>>> each codec configuration.<br>
>>><br>
>>> set codec0.compressor zlib<br>
>>> set codec0.compressor_level 6<br>
>>><br>
>>> But actually, it would probably be best for you to just update and<br>
>>> rebuild without changing your configuration. Just do "svn up" at the<br>
>>> top level directory and do "make clean" and "make" in<br>
>>> programs/wanproxy.<br>
>>><br>
>>> Thanks!<br>
>>> Juli.<br>
>>><br>
>>> On Sun, Dec 18, 2011 at 14:28, Ali Jawad <<a href="mailto:alijawad1@gmail.com">alijawad1@gmail.com</a>> wrote:<br>
>>> > Hi<br>
>>> > First of all, let me express my appreciations for all the support and<br>
>>> > help,<br>
>>> > Open source products are the result of collaboration between the people<br>
>>> > who<br>
>>> > do the hard work like yourself, and people who make use of the<br>
>>> > creativity/productivity of people like yourself, that would be me :).<br>
>>> > So I<br>
>>> > do not mind doing some testing and debugging.<br>
>>> > Having said that, you want me to make clean and make recompile at the<br>
>>> > trunk<br>
>>> > level ? How to test without zlib/zcodec ? Removing parts of config ?<br>
>>> > The<br>
>>> > only binary I am using is wanproxy that I copied to /usr/sbin/ did I<br>
>>> > miss<br>
>>> > something here ? What is the second binary ?<br>
>>> > Regards<br>
>>> ><br>
>>> > On Mon, Dec 19, 2011 at 1:24 AM, Juli Mallett <<a href="mailto:juli@clockworksquid.com">juli@clockworksquid.com</a>><br>
>>> > wrote:<br>
>>> >><br>
>>> >> I thought I had fixed this problem. You are using both zlib and<br>
>>> >> xcodec, right? I do not understand how this error could still be<br>
>>> >> happening. If you could try with only xcodec or only zlib, that might<br>
>>> >> be helpful to me, so I know which component is in need of further<br>
>>> >> testing.<br>
>>> >><br>
>>> >> Also, if you want to update the whole tree and rebuild both binaries,<br>
>>> >> I've added some messages which should make it easier to tell which<br>
>>> >> PipeProducer subclass is doing the wrong thing here.<br>
>>> >><br>
>>> >> Apologies for all the difficulty. I want you to know that I have been<br>
>>> >> testing this, and did originally see the problem you report here, but<br>
>>> >> did find a way to fix it. I have some work I need to do today that I<br>
>>> >> do not want to disrupt, but I am hoping that later in my evening (I'm<br>
>>> >> on the west coast of the US) I will be able to set up a few more<br>
>>> >> systems to use in testing, and see if I can trigger this bug.<br>
>>> >><br>
>>> >> On Sun, Dec 18, 2011 at 05:21, Ali Jawad <<a href="mailto:alijawad1@gmail.com">alijawad1@gmail.com</a>> wrote:<br>
>>> >> > Hi<br>
>>> >> > Client crashed when a page displayed flash, with following error<br>
>>> >> ><br>
>>> >> > 1324214230.331051 [/assert] EMERG: void<br>
>>> >> > PipeProducer::produce(Buffer*):<br>
>>> >> > Halting: Assertion (!output_eos_) failed at<br>
>>> >> > ../../io/pipe/pipe_producer.cc:109 in function void<br>
>>> >> > PipeProducer::produce(Buffer*).<br>
>>> >> > Aborted<br>
>>> >> ><br>
>>> >> > Regards<br>
>>> >> ><br>
>>> >> > On Sun, Dec 18, 2011 at 3:55 PM, Ali Jawad <<a href="mailto:alijawad1@gmail.com">alijawad1@gmail.com</a>><br>
>>> >> > wrote:<br>
>>> >> >><br>
>>> >> >> Hi July<br>
>>> >> >> I was able to make the connection work, it was a stupid mistake on<br>
>>> >> >> my<br>
>>> >> >> side, the errors are less and performance is slightly better but<br>
>>> >> >> still<br>
>>> >> >> slow<br>
>>> >> >> I am getting these errors on client side now<br>
>>> >> >><br>
>>> >> >> 1324212755.168570 [/wanproxy/proxy/proxy0/connector] ERR: void<br>
>>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:<br>
>>> >> >> <Error>/104<br>
>>> >> >> [Connection reset by peer]<br>
>>> >> >> 1324212756.652634 [/wanproxy/proxy/proxy0/connector] ERR: void<br>
>>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:<br>
>>> >> >> <Error>/104<br>
>>> >> >> [Connection reset by peer]<br>
>>> >> >> 1324212776.041883 [/wanproxy/proxy/proxy0/connector] ERR: void<br>
>>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:<br>
>>> >> >> <Error>/104<br>
>>> >> >> [Connection reset by peer]<br>
>>> >> >> 1324212777.468335 [/wanproxy/proxy/proxy0/connector] ERR: void<br>
>>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:<br>
>>> >> >> <Error>/104<br>
>>> >> >> [Connection reset by peer]<br>
>>> >> >><br>
>>> >> >> On server side I am getting<br>
>>> >> >><br>
>>> >> >> 1324184191.330804 [/wanproxy/proxy/proxy-socks0/connector] ERR:<br>
>>> >> >> void<br>
>>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:<br>
>>> >> >> <Error>/104<br>
>>> >> >> [Connection reset by peer]<br>
>>> >> >> 1324184194.297132 [/wanproxy/proxy/proxy-socks0/connector] ERR:<br>
>>> >> >> void<br>
>>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:<br>
>>> >> >> <Error>/104<br>
>>> >> >> [Connection reset by peer]<br>
>>> >> >> 1324184202.948238 [/wanproxy/proxy/proxy-socks0/connector] ERR:<br>
>>> >> >> void<br>
>>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:<br>
>>> >> >> <Error>/104<br>
>>> >> >> [Connection reset by peer]<br>
>>> >> >> 1324184202.951848 [/wanproxy/proxy/proxy-socks0/connector] ERR:<br>
>>> >> >> void<br>
>>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:<br>
>>> >> >> <Error>/104<br>
>>> >> >> [Connection reset by peer]<br>
>>> >> >> 1324184217.752559 [/wanproxy/proxy/proxy-socks0/connector] ERR:<br>
>>> >> >> void<br>
>>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:<br>
>>> >> >> <Error>/104<br>
>>> >> >> [Connection reset by peer]<br>
>>> >> >> 1324184217.755806 [/wanproxy/proxy/proxy-socks0/connector] ERR:<br>
>>> >> >> void<br>
>>> >> >> ProxyConnector::splice_complete(Event): Unexpected event:<br>
>>> >> >> <Error>/104<br>
>>> >> >> [Connection reset by peer]<br>
>>> >> >><br>
>>> >> >><br>
>>> >> >><br>
>>> >> >> Regards<br>
>>> >> >><br>
>>> >> >> On Sun, Dec 18, 2011 at 3:06 AM, Juli Mallett<br>
>>> >> >> <<a href="mailto:juli@clockworksquid.com">juli@clockworksquid.com</a>><br>
>>> >> >> wrote:<br>
>>> >> >>><br>
>>> >> >>> Very strange. Can you send the client and server configurations?<br>
>>> >> >>> I'm<br>
>>> >> >>> guessing that connect is failing because the ports are mismatched<br>
>>> >> >>> or<br>
>>> >> >>> similar, but I can't be sure. It would also be helpful if you<br>
>>> >> >>> could<br>
>>> >> >>> telnet from the client to the port the server is supposed to be<br>
>>> >> >>> listening on, to verify that there are no firewalling issues<br>
>>> >> >>> involved.<br>
>>> >> >>><br>
>>> >> >>> On Sat, Dec 17, 2011 at 15:21, Ali Jawad <<a href="mailto:alijawad1@gmail.com">alijawad1@gmail.com</a>><br>
>>> >> >>> wrote:<br>
>>> >> >>> > Hi Juli<br>
>>> >> >>> > Did checkout to version 895 on both machines and did the<br>
>>> >> >>> > following<br>
>>> >> >>> > on<br>
>>> >> >>> > both<br>
>>> >> >>> > machines as well , make clean in programs/wanproxy, make, copy<br>
>>> >> >>> > wanproxy<br>
>>> >> >>> > file<br>
>>> >> >>> > to /usr/sbin/ then launch<br>
>>> >> >>> ><br>
>>> >> >>> > /usr/sbin/wanproxy -c /etc/wanproxy.conf<br>
>>> >> >>> ><br>
>>> >> >>> > On the client I get<br>
>>> >> >>> ><br>
>>> >> >>> > 1324163928.337113 [/wanproxy/proxy/proxy0/listener] INFO:<br>
>>> >> >>> > Listening<br>
>>> >> >>> > on:<br>
>>> >> >>> > [0.0.0.0]:3300<br>
>>> >> >>> > 1324163928.337732 [/event/thread] INFO: Starting event thread.<br>
>>> >> >>> > 1324163930.640914 [/wanproxy/proxy/proxy0/connector] INFO:<br>
>>> >> >>> > Connect<br>
>>> >> >>> > failed:<br>
>>> >> >>> > <Error>/0 [Success]<br>
>>> >> >>> > 1324163931.393061 [/wanproxy/proxy/proxy0/connector] INFO:<br>
>>> >> >>> > Connect<br>
>>> >> >>> > failed:<br>
>>> >> >>> > <Error>/0 [Success]<br>
>>> >> >>> > 1324163932.144333 [/wanproxy/proxy/proxy0/connector] INFO:<br>
>>> >> >>> > Connect<br>
>>> >> >>> > failed:<br>
>>> >> >>> > <Error>/0 [Success]<br>
>>> >> >>> > 1324163932.919439 [/wanproxy/proxy/proxy0/connector] INFO:<br>
>>> >> >>> > Connect<br>
>>> >> >>> > failed:<br>
>>> >> >>> > <Error>/0 [Success]<br>
>>> >> >>> > 1324163933.906755 [/wanproxy/proxy/proxy0/connector] INFO:<br>
>>> >> >>> > Connect<br>
>>> >> >>> > failed:<br>
>>> >> >>> > <Error>/0 [Success]<br>
>>> >> >>> > 1324163934.677630 [/wanproxy/proxy/proxy0/connector] INFO:<br>
>>> >> >>> > Connect<br>
>>> >> >>> > failed:<br>
>>> >> >>> > <Error>/0 [Success]<br>
>>> >> >>> > 1324163935.459671 [/wanproxy/proxy/proxy0/connector] INFO:<br>
>>> >> >>> > Connect<br>
>>> >> >>> > failed:<br>
>>> >> >>> > <Error>/0 [Success]<br>
>>> >> >>> ><br>
>>> >> >>> ><br>
>>> >> >>> > And the browser is not working when setting socks to use<br>
>>> >> >>> > wanproxy<br>
>>> >> >>> > client.<br>
>>> >> >>> > Anything I missed here ?<br>
>>> >> >>> ><br>
>>> >> >>> > Thanks<br>
>>> >> >>> ><br>
>>> >> >>> > On Sun, Dec 18, 2011 at 2:02 AM, Ali Jawad <<a href="mailto:alijawad1@gmail.com">alijawad1@gmail.com</a>><br>
>>> >> >>> > wrote:<br>
>>> >> >>> >><br>
>>> >> >>> >> Hi<br>
>>> >> >>> >> The problem happened on the latest trunk that I donwload just<br>
>>> >> >>> >> after<br>
>>> >> >>> >> your<br>
>>> >> >>> >> latest email, I will checkout trunk, clean and make and send<br>
>>> >> >>> >> output.<br>
>>> >> >>> >> Thank agains<br>
>>> >> >>> >> Regards<br>
>>> >> >>> >><br>
>>> >> >>> >><br>
>>> >> >>> >> On Sun, Dec 18, 2011 at 12:27 AM, Juli Mallett<br>
>>> >> >>> >> <<a href="mailto:juli@clockworksquid.com">juli@clockworksquid.com</a>><br>
>>> >> >>> >> wrote:<br>
>>> >> >>> >>><br>
>>> >> >>> >>> First, update to latest trunk since I fixed the issues you've<br>
>>> >> >>> >>> reported so<br>
>>> >> >>> >>> far.<br>
>>> >> >>> >>><br>
>>> >> >>> >>> Then could you go to programs/wanproxy on the client, "make<br>
>>> >> >>> >>> clean",<br>
>>> >> >>> >>> and then send all of the output of "make" to the list?<br>
>>> >> >>> >>><br>
>>> >> >>> >>> Thanks!<br>
>>> >> >>> >>> Juli.<br>
>>> >> >>> >>><br>
>>> >> >>> >>> On Sat, Dec 17, 2011 at 13:23, Ali Jawad <<a href="mailto:alijawad1@gmail.com">alijawad1@gmail.com</a>><br>
>>> >> >>> >>> wrote:<br>
>>> >> >>> >>> > Hi Juli<br>
>>> >> >>> >>> > Thanks for the continous help, I have one on the latest<br>
>>> >> >>> >>> > trunk,<br>
>>> >> >>> >>> > but<br>
>>> >> >>> >>> > the<br>
>>> >> >>> >>> > client I get errors while compiling the trunk on, the<br>
>>> >> >>> >>> > problem is<br>
>>> >> >>> >>> > related to<br>
>>> >> >>> >>> > this it seems "result of make in programs/wanproxy/"<br>
>>> >> >>> >>> ><br>
>>> >> >>> >>> >>> cc1plus: warnings being treated as errors<br>
>>> >> >>> >>> >>> ../../io/socket/simple_server.h: In instantiation of<br>
>>> >> >>> >>> >>> ‘SimpleServer<TCPServer>’:<br>
>>> >> >>> >>> >>> proxy_listener.h:10: instantiated from here<br>
>>> >> >>> >>> >>> ../../io/socket/simple_server.h:12: warning: ‘class<br>
>>> >> >>> >>> >>> SimpleServer<TCPServer>’ has virtual functions but<br>
>>> >> >>> >>> >>> non-virtual<br>
>>> >> >>> >>> >>> destructor<br>
>>> >> >>> >>> >>> proxy_listener.h:10: warning: ‘class ProxyListener’ has<br>
>>> >> >>> >>> >>> virtual<br>
>>> >> >>> >>> >>> functions<br>
>>> >> >>> >>> >>> but non-virtual destructor<br>
>>> >> >>> >>> >>> make: *** [proxy_listener.o] Error 1<br>
>>> >> >>> >>> ><br>
>>> >> >>> >>> > On Sun, Dec 18, 2011 at 12:12 AM, Juli Mallett<br>
>>> >> >>> >>> > <<a href="mailto:juli@clockworksquid.com">juli@clockworksquid.com</a>><br>
>>> >> >>> >>> > wrote:<br>
>>> >> >>> >>> >><br>
>>> >> >>> >>> >> Hi Ali,<br>
>>> >> >>> >>> >><br>
>>> >> >>> >>> >> Thanks for pointing out the problems with<br>
>>> >> >>> >>> >> -Wnon-virtual-dtor —<br>
>>> >> >>> >>> >> I<br>
>>> >> >>> >>> >> fixed<br>
>>> >> >>> >>> >> those just now.<br>
>>> >> >>> >>> >><br>
>>> >> >>> >>> >> You need to have the client and server running the same<br>
>>> >> >>> >>> >> version.<br>
>>> >> >>> >>> >> The<br>
>>> >> >>> >>> >> protocol has changed considerable from 0.7.2 to today, and<br>
>>> >> >>> >>> >> you<br>
>>> >> >>> >>> >> should<br>
>>> >> >>> >>> >> not mix the two.<br>
>>> >> >>> >>> >><br>
>>> >> >>> >>> >> That said, I think you may have some other problem with the<br>
>>> >> >>> >>> >> errors<br>
>>> >> >>> >>> >> you're seeing; I don't think the mix of versions would<br>
>>> >> >>> >>> >> explain<br>
>>> >> >>> >>> >> it.<br>
>>> >> >>> >>> >> Still, if you would update both to trunk and report any<br>
>>> >> >>> >>> >> issues<br>
>>> >> >>> >>> >> you<br>
>>> >> >>> >>> >> encounter back, I'll try to fix them as soon as possible.<br>
>>> >> >>> >>> >> If<br>
>>> >> >>> >>> >> you<br>
>>> >> >>> >>> >> continue to experience issues, I'll set up a CentOS VM to<br>
>>> >> >>> >>> >> test<br>
>>> >> >>> >>> >> everything myself before asking you to do so again.<br>
>>> >> >>> >>> >><br>
>>> >> >>> >>> >> Sorry about the continued difficulty. I usually try very<br>
>>> >> >>> >>> >> hard<br>
>>> >> >>> >>> >> to<br>
>>> >> >>> >>> >> make<br>
>>> >> >>> >>> >> sure users have a seamless experience of building and using<br>
>>> >> >>> >>> >> WANProxy.<br>
>>> >> >>> >>> >> Once this is all resolved, I'll put out a release tarball,<br>
>>> >> >>> >>> >> too.<br>
>>> >> >>> >>> >><br>
>>> >> >>> >>> >> Thanks,<br>
>>> >> >>> >>> >> Juli.<br>
>>> >> >>> >>> >><br>
>>> >> >>> >>> >> On Sat, Dec 17, 2011 at 05:44, Ali Jawad<br>
>>> >> >>> >>> >> <<a href="mailto:alijawad1@gmail.com">alijawad1@gmail.com</a>><br>
>>> >> >>> >>> >> wrote:<br>
>>> >> >>> >>> >> > Right now using latest trunk for server, and latest tgz<br>
>>> >> >>> >>> >> > for<br>
>>> >> >>> >>> >> > client<br>
>>> >> >>> >>> >> > I am<br>
>>> >> >>> >>> >> > getting this error<br>
>>> >> >>> >>> >> ><br>
>>> >> >>> >>> >> > [root@CentOS54 programs]# /usr/sbin/wanproxy -c<br>
>>> >> >>> >>> >> > /etc/wanproxy.conf<br>
>>> >> >>> >>> >> > 1324129297.168662 [/wanproxy] INFO: WANProxy 0.7.2<br>
>>> >> >>> >>> >> > 1324129297.169621 [/wanproxy] INFO: Copyright (c)<br>
>>> >> >>> >>> >> > 2008-2011<br>
>>> >> >>> >>> >> > WANProxy.org.<br>
>>> >> >>> >>> >> > 1324129297.170510 [/wanproxy] INFO: All rights reserved.<br>
>>> >> >>> >>> >> > 1324129297.171419 [/wanproxy/config] INFO: Configuring<br>
>>> >> >>> >>> >> > WANProxy.<br>
>>> >> >>> >>> >> > 1324129297.173140 [/io/system] INFO: Starting IO system.<br>
>>> >> >>> >>> >> > 1324129297.173861 [/event/thread] INFO: Starting event<br>
>>> >> >>> >>> >> > thread.<br>
>>> >> >>> >>> >> > 1324129319.092574 [/wanproxy/proxy/proxy0/connector]<br>
>>> >> >>> >>> >> > INFO:<br>
>>> >> >>> >>> >> > Connect<br>
>>> >> >>> >>> >> > failed:<br>
>>> >> >>> >>> >> > <Error>/0 [Success]<br>
>>> >> >>> >>> >> > 1324129319.895308 [/wanproxy/proxy/proxy0/connector]<br>
>>> >> >>> >>> >> > INFO:<br>
>>> >> >>> >>> >> > Connect<br>
>>> >> >>> >>> >> > failed:<br>
>>> >> >>> >>> >> > <Error>/0 [Success]<br>
>>> >> >>> >>> >> > 1324129320.699028 [/wanproxy/proxy/proxy0/connector]<br>
>>> >> >>> >>> >> > INFO:<br>
>>> >> >>> >>> >> > Connect<br>
>>> >> >>> >>> >> > failed:<br>
>>> >> >>> >>> >> > <Error>/0 [Success]<br>
>>> >> >>> >>> >> > 1324129321.499178 [/wanproxy/proxy/proxy0/connector]<br>
>>> >> >>> >>> >> > INFO:<br>
>>> >> >>> >>> >> > Connect<br>
>>> >> >>> >>> >> > failed:<br>
>>> >> >>> >>> >> > <Error>/0 [Success]<br>
>>> >> >>> >>> >> ><br>
>>> >> >>> >>> >> ><br>
>>> >> >>> >>> >> > On Sat, Dec 17, 2011 at 4:33 PM, Ali Jawad<br>
>>> >> >>> >>> >> > <<a href="mailto:alijawad1@gmail.com">alijawad1@gmail.com</a>><br>
>>> >> >>> >>> >> > wrote:<br>
>>> >> >>> >>> >> >><br>
>>> >> >>> >>> >> >> If I go to the programs/wanproxy and just make there I<br>
>>> >> >>> >>> >> >> get<br>
>>> >> >>> >>> >> >><br>
>>> >> >>> >>> >> >> cc1plus: warnings being treated as errors<br>
>>> >> >>> >>> >> >> ../../io/socket/simple_server.h: In instantiation of<br>
>>> >> >>> >>> >> >> ‘SimpleServer<TCPServer>’:<br>
>>> >> >>> >>> >> >> proxy_listener.h:10: instantiated from here<br>
>>> >> >>> >>> >> >> ../../io/socket/simple_server.h:12: warning: ‘class<br>
>>> >> >>> >>> >> >> SimpleServer<TCPServer>’ has virtual functions but<br>
>>> >> >>> >>> >> >> non-virtual<br>
>>> >> >>> >>> >> >> destructor<br>
>>> >> >>> >>> >> >> proxy_listener.h:10: warning: ‘class ProxyListener’ has<br>
>>> >> >>> >>> >> >> virtual<br>
>>> >> >>> >>> >> >> functions<br>
>>> >> >>> >>> >> >> but non-virtual destructor<br>
>>> >> >>> >>> >> >> make: *** [proxy_listener.o] Error 1<br>
>>> >> >>> >>> >> >><br>
>>> >> >>> >>> >> >><br>
>>> >> >>> >>> >> >> On Fri, Dec 16, 2011 at 3:21 PM, Juli Mallett<br>
>>> >> >>> >>> >> >> <<a href="mailto:juli@clockworksquid.com">juli@clockworksquid.com</a>><br>
>>> >> >>> >>> >> >> wrote:<br>
>>> >> >>> >>> >> >>><br>
>>> >> >>> >>> >> >>> Hi Ali,<br>
>>> >> >>> >>> >> >>><br>
>>> >> >>> >>> >> >>> The problems you encountered should be fixed in<br>
>>> >> >>> >>> >> >>> Subversion.<br>
>>> >> >>> >>> >> >>> Can<br>
>>> >> >>> >>> >> >>> you<br>
>>> >> >>> >>> >> >>> please provide the errors you encountered? Most<br>
>>> >> >>> >>> >> >>> commonly,<br>
>>> >> >>> >>> >> >>> the<br>
>>> >> >>> >>> >> >>> problem<br>
>>> >> >>> >>> >> >>> is missing libuuid-dev or similar package, at least on<br>
>>> >> >>> >>> >> >>> Linux<br>
>>> >> >>> >>> >> >>> systems.<br>
>>> >> >>> >>> >> >>><br>
>>> >> >>> >>> >> >>> Thanks!<br>
>>> >> >>> >>> >> >>> Juli.<br>
>>> >> >>> >>> >> >>><br>
>>> >> >>> >>> >> >>> On Wed, Dec 14, 2011 at 06:56, Ali Jawad<br>
>>> >> >>> >>> >> >>> <<a href="mailto:alijawad1@gmail.com">alijawad1@gmail.com</a>><br>
>>> >> >>> >>> >> >>> wrote:<br>
>>> >> >>> >>> >> >>> > Hi<br>
>>> >> >>> >>> >> >>> > I tried to install latest src code but did only run<br>
>>> >> >>> >>> >> >>> > in to<br>
>>> >> >>> >>> >> >>> > problems<br>
>>> >> >>> >>> >> >>> > during compiling, but 0.7.2 did not face any issues,<br>
>>> >> >>> >>> >> >>> > did<br>
>>> >> >>> >>> >> >>> > you<br>
>>> >> >>> >>> >> >>> > face<br>
>>> >> >>> >>> >> >>> > problems with websites opening during that error ?<br>
>>> >> >>> >>> >> >>> > Regards<br>
>>> >> >>> >>> >> >>> ><br>
>>> >> >>> >>> >> >>> > On Wed, Dec 14, 2011 at 3:39 PM, Diego Woitasen<br>
>>> >> >>> >>> >> >>> > <<a href="mailto:diego@woitasen.com.ar">diego@woitasen.com.ar</a>><br>
>>> >> >>> >>> >> >>> > wrote:<br>
>>> >> >>> >>> >> >>> >> On Tue, Dec 13, 2011 at 6:17 PM, Juli Mallett<br>
>>> >> >>> >>> >> >>> >> <<a href="mailto:juli@clockworksquid.com">juli@clockworksquid.com</a>> wrote:<br>
>>> >> >>> >>> >> >>> >>> Hi Ali,<br>
>>> >> >>> >>> >> >>> >>><br>
>>> >> >>> >>> >> >>> >>> On Tue, Dec 13, 2011 at 13:08, Ali Jawad<br>
>>> >> >>> >>> >> >>> >>> <<a href="mailto:alijawad1@gmail.com">alijawad1@gmail.com</a>><br>
>>> >> >>> >>> >> >>> >>> wrote:<br>
>>> >> >>> >>> >> >>> >>>> and on the client I am getting<br>
>>> >> >>> >>> >> >>> >>>><br>
>>> >> >>> >>> >> >>> >>>> 1323524646.018556<br>
>>> >> >>> >>> >> >>> >>>> [/wanproxy/proxy/proxy0/connector]<br>
>>> >> >>> >>> >> >>> >>>> ERR:<br>
>>> >> >>> >>> >> >>> >>>> void<br>
>>> >> >>> >>> >> >>> >>>> ProxyConnector::splice_complete(Event): Unexpected<br>
>>> >> >>> >>> >> >>> >>>> event:<br>
>>> >> >>> >>> >> >>> >>>> <Error>/32<br>
>>> >> >>> >>> >> >>> >>>> [Broken pipe]<br>
>>> >> >>> >>> >> >>> >>>> 1323524690.407944 [/assert] EMERG: void<br>
>>> >> >>> >>> >> >>> >>>> PipeProducer::produce(Buffer*): Halting: Assertion<br>
>>> >> >>> >>> >> >>> >>>> (!output_eos_)<br>
>>> >> >>> >>> >> >>> >>>> failed at ../../io/pipe/pipe_producer.cc:109 in<br>
>>> >> >>> >>> >> >>> >>>> function<br>
>>> >> >>> >>> >> >>> >>>> void<br>
>>> >> >>> >>> >> >>> >>>> PipeProducer::produce(Buffer*).<br>
>>> >> >>> >>> >> >>> >>>> Aborted<br>
>>> >> >>> >>> >> >>> >>><br>
>>> >> >>> >>> >> >>> >>> Thanks. Several other users have reported this,<br>
>>> >> >>> >>> >> >>> >>> but I<br>
>>> >> >>> >>> >> >>> >>> have<br>
>>> >> >>> >>> >> >>> >>> not<br>
>>> >> >>> >>> >> >>> >>> been<br>
>>> >> >>> >>> >> >>> >>> able to reproduce it. I will redouble my efforts<br>
>>> >> >>> >>> >> >>> >>> to<br>
>>> >> >>> >>> >> >>> >>> reproduce.<br>
>>> >> >>> >>> >> >>> >>><br>
>>> >> >>> >>> >> >>> >>>> On Tue, Dec 13, 2011 at 3:06 AM, Ali Jawad<br>
>>> >> >>> >>> >> >>> >>>> <<a href="mailto:alijawad1@gmail.com">alijawad1@gmail.com</a>><br>
>>> >> >>> >>> >> >>> >>>> wrote:<br>
>>> >> >>> >>> >> >>> >>>>> Hi<br>
>>> >> >>> >>> >> >>> >>>>> Browsers are FF 4.x and 3.x on Windows and Linux,<br>
>>> >> >>> >>> >> >>> >>>>> I<br>
>>> >> >>> >>> >> >>> >>>>> also<br>
>>> >> >>> >>> >> >>> >>>>> tried<br>
>>> >> >>> >>> >> >>> >>>>> IE8,<br>
>>> >> >>> >>> >> >>> >>>>> the config is the same one given in the examples,<br>
>>> >> >>> >>> >> >>> >>>>> the<br>
>>> >> >>> >>> >> >>> >>>>> OS<br>
>>> >> >>> >>> >> >>> >>>>> is<br>
>>> >> >>> >>> >> >>> >>>>> CentOS<br>
>>> >> >>> >>> >> >>> >>>>> 5.6<br>
>>> >> >>> >>> >> >>> >>>>> 64bit.<br>
>>> >> >>> >>> >> >>> >>>>> Regards<br>
>>> >> >>> >>> >> >>> >>>>><br>
>>> >> >>> >>> >> >>> >>>>> On Mon, Dec 12, 2011 at 12:48 AM, Juli Mallett<br>
>>> >> >>> >>> >> >>> >>>>> <<a href="mailto:juli@clockworksquid.com">juli@clockworksquid.com</a>> wrote:<br>
>>> >> >>> >>> >> >>> >>>>>> Thanks for the feedback. I don't think I will<br>
>>> >> >>> >>> >> >>> >>>>>> need<br>
>>> >> >>> >>> >> >>> >>>>>> access,<br>
>>> >> >>> >>> >> >>> >>>>>> but<br>
>>> >> >>> >>> >> >>> >>>>>> I<br>
>>> >> >>> >>> >> >>> >>>>>> may<br>
>>> >> >>> >>> >> >>> >>>>>> need more configuration information to<br>
>>> >> >>> >>> >> >>> >>>>>> reproduce.<br>
>>> >> >>> >>> >> >>> >>>>>> What<br>
>>> >> >>> >>> >> >>> >>>>>> OS<br>
>>> >> >>> >>> >> >>> >>>>>> is<br>
>>> >> >>> >>> >> >>> >>>>>> WANProxy<br>
>>> >> >>> >>> >> >>> >>>>>> running on? Can you send your configuration?<br>
>>> >> >>> >>> >> >>> >>>>>> What<br>
>>> >> >>> >>> >> >>> >>>>>> browser<br>
>>> >> >>> >>> >> >>> >>>>>> is<br>
>>> >> >>> >>> >> >>> >>>>>> the<br>
>>> >> >>> >>> >> >>> >>>>>> client?<br>
>>> >> >>> >>> >> >>> >>>>>><br>
>>> >> >>> >>> >> >>> >>>>>> Thanks!<br>
>>> >> >>> >>> >> >>> >>>>>><br>
>>> >> >>> >>> >> >>> >>>>>> On Sun, Dec 11, 2011 at 13:44, Ali Jawad<br>
>>> >> >>> >>> >> >>> >>>>>> <<a href="mailto:alijawad1@gmail.com">alijawad1@gmail.com</a>><br>
>>> >> >>> >>> >> >>> >>>>>> wrote:<br>
>>> >> >>> >>> >> >>> >>>>>>> Hi<br>
>>> >> >>> >>> >> >>> >>>>>>> Thanks for the help so far, I might be able to<br>
>>> >> >>> >>> >> >>> >>>>>>> give<br>
>>> >> >>> >>> >> >>> >>>>>>> you<br>
>>> >> >>> >>> >> >>> >>>>>>> access<br>
>>> >> >>> >>> >> >>> >>>>>>> to<br>
>>> >> >>> >>> >> >>> >>>>>>> check it out if needed, as for now no IPV6,<br>
>>> >> >>> >>> >> >>> >>>>>>> sites<br>
>>> >> >>> >>> >> >>> >>>>>>> like<br>
>>> >> >>> >>> >> >>> >>>>>>> cnn<br>
>>> >> >>> >>> >> >>> >>>>>>> youtube etc<br>
>>> >> >>> >>> >> >>> >>>>>>> Regards<br>
>>> >> >>> >>> >> >>> >>>>>>><br>
>>> >> >>> >>> >> >>> >>>>>>> On Mon, Dec 12, 2011 at 12:34 AM, Juli Mallett<br>
>>> >> >>> >>> >> >>> >>>>>>> <<a href="mailto:juli@clockworksquid.com">juli@clockworksquid.com</a>> wrote:<br>
>>> >> >>> >>> >> >>> >>>>>>>> This seems very strange. Which sites? Do you<br>
>>> >> >>> >>> >> >>> >>>>>>>> have<br>
>>> >> >>> >>> >> >>> >>>>>>>> IPv6<br>
>>> >> >>> >>> >> >>> >>>>>>>> connectivity?<br>
>>> >> >>> >>> >> >>> >>>>>>>> If you don't have IPv6 connectivity, I wonder<br>
>>> >> >>> >>> >> >>> >>>>>>>> if<br>
>>> >> >>> >>> >> >>> >>>>>>>> that<br>
>>> >> >>> >>> >> >>> >>>>>>>> might<br>
>>> >> >>> >>> >> >>> >>>>>>>> be<br>
>>> >> >>> >>> >> >>> >>>>>>>> the<br>
>>> >> >>> >>> >> >>> >>>>>>>> problem, and we might need some way to tell<br>
>>> >> >>> >>> >> >>> >>>>>>>> WANProxy<br>
>>> >> >>> >>> >> >>> >>>>>>>> to<br>
>>> >> >>> >>> >> >>> >>>>>>>> use<br>
>>> >> >>> >>> >> >>> >>>>>>>> IPv4<br>
>>> >> >>> >>> >> >>> >>>>>>>> only.<br>
>>> >> >>> >>> >> >>> >>>>>>>> If you have specific examples that likely<br>
>>> >> >>> >>> >> >>> >>>>>>>> will<br>
>>> >> >>> >>> >> >>> >>>>>>>> make<br>
>>> >> >>> >>> >> >>> >>>>>>>> it<br>
>>> >> >>> >>> >> >>> >>>>>>>> easier<br>
>>> >> >>> >>> >> >>> >>>>>>>> for me<br>
>>> >> >>> >>> >> >>> >>>>>>>> to reproduce and fix.<br>
>>> >> >>> >>> >> >>> >>>>>>>><br>
>>> >> >>> >>> >> >>> >>>>>>>> Thanks & sorry to hear about your difficulty,<br>
>>> >> >>> >>> >> >>> >>>>>>>> Juli.<br>
>>> >> >>> >>> >> >>> >>>>>>>><br>
>>> >> >>> >>> >> >>> >>>>>>>> On Sun, Dec 11, 2011 at 12:04, Ali Jawad<br>
>>> >> >>> >>> >> >>> >>>>>>>> <<a href="mailto:alijawad1@gmail.com">alijawad1@gmail.com</a>><br>
>>> >> >>> >>> >> >>> >>>>>>>> wrote:<br>
>>> >> >>> >>> >> >>> >>>>>>>>> Hi<br>
>>> >> >>> >>> >> >>> >>>>>>>>> I completed the setup, but some sites open<br>
>>> >> >>> >>> >> >>> >>>>>>>>> and<br>
>>> >> >>> >>> >> >>> >>>>>>>>> some<br>
>>> >> >>> >>> >> >>> >>>>>>>>> not,<br>
>>> >> >>> >>> >> >>> >>>>>>>>> some<br>
>>> >> >>> >>> >> >>> >>>>>>>>> sites<br>
>>> >> >>> >>> >> >>> >>>>>>>>> need to be reloaded a few times for it to<br>
>>> >> >>> >>> >> >>> >>>>>>>>> work,<br>
>>> >> >>> >>> >> >>> >>>>>>>>> I.e.<br>
>>> >> >>> >>> >> >>> >>>>>>>>> CSS<br>
>>> >> >>> >>> >> >>> >>>>>>>>> does<br>
>>> >> >>> >>> >> >>> >>>>>>>>> not load<br>
>>> >> >>> >>> >> >>> >>>>>>>>> etc.<br>
>>> >> >>> >>> >> >>> >>>>>>>>> Any ideas ?<br>
>>> >> >>> >>> >> >>> >>>>>>>>> Regards<br>
>>> >> >>> >>> >> >>> >>>>>>>>><br>
>>> >> >>> >>> >> >>> >>>>>>>>> On Mon, Dec 5, 2011 at 12:27 AM, Juli Mallett<br>
>>> >> >>> >>> >> >>> >>>>>>>>> <<a href="mailto:juli@clockworksquid.com">juli@clockworksquid.com</a>> wrote:<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> Hi Ali,<br>
>>> >> >>> >>> >> >>> >>>>>>>>>><br>
>>> >> >>> >>> >> >>> >>>>>>>>>> If you already have the SOCKS example<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> configured,<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> then<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> you<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> should be<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> able to use your browser or operating<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> system's<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> proxy<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> configuration to<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> tell it to use SOCKS for HTTP or FTP or<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> whatever<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> protocols<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> you<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> need.<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> If you have trouble finding this and tell us<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> what<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> OS<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> and<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> browser or<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> other software you're using I'm sure one of<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> us<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> can<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> help<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> you<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> get the<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> information you need!<br>
>>> >> >>> >>> >> >>> >>>>>>>>>><br>
>>> >> >>> >>> >> >>> >>>>>>>>>> Thanks,<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> Juli.<br>
>>> >> >>> >>> >> >>> >>>>>>>>>><br>
>>> >> >>> >>> >> >>> >>>>>>>>>> On Sun, Dec 4, 2011 at 03:26, Ali Jawad<br>
>>> >> >>> >>> >> >>> >>>>>>>>>> <<a href="mailto:alijawad1@gmail.com">alijawad1@gmail.com</a>><br>
>>> >> >>> >>> >> >>> >>>>>>>>>> wrote:<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> Hi<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> I did setup wanproxy in client/server mode<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> as<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> per<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> the<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> Proxying over a<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> WAN using SOCKS example in<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> <a href="http://wanproxy.org/examples.shtml" target="_blank">http://wanproxy.org/examples.shtml</a><br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> . Here<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> is the issue<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>><br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> I do have a server in Asia which is the<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> client<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> and<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> a<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> server<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> in the USA<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> which is the wanproxy server, I want<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> traffic<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> for<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> browsing<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> to<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> pass<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> through the wanproxy link and from there on<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> fetch<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> the<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> sites I<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> need in<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> the states and send them back after that<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> through<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> the<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> WAN<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> link<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> to the<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> client server which sends them to the<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> browser<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> of<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> the<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> client<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> in my LAN.<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>><br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> Is this something WAN proxy does ? Do I<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> need to<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> do<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> additional<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> stuff ?<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> Such as setting up SQUID on wanproxy server<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> or<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> client<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> server<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> ? Is any<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> ip forwarding needed ? What configuration<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> should I<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> use<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> on<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> the<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> browsers<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> ?<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>><br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> I am sorry for the long list of questions,<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> but<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> I<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> am<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> sure<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> it<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> will come<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> in handy for people who research the topic<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> online<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> "once<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> answered that<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> is :)"<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>><br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> Thanks !<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>><br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> _______________________________________________<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> wanproxy mailing list<br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> <a href="mailto:wanproxy@lists.wanproxy.org">wanproxy@lists.wanproxy.org</a><br>
>>> >> >>> >>> >> >>> >>>>>>>>>>><br>
>>> >> >>> >>> >> >>> >>>>>>>>>>><br>
>>> >> >>> >>> >> >>> >>>>>>>>>>><br>
>>> >> >>> >>> >> >>> >>>>>>>>>>><br>
>>> >> >>> >>> >> >>> >>>>>>>>>>><br>
>>> >> >>> >>> >> >>> >>>>>>>>>>> <a href="http://lists.wanproxy.org/listinfo.cgi/wanproxy-wanproxy.org" target="_blank">http://lists.wanproxy.org/listinfo.cgi/wanproxy-wanproxy.org</a><br>
>>> >> >>> >>> >> >>> >>> _______________________________________________<br>
>>> >> >>> >>> >> >>> >>> wanproxy mailing list<br>
>>> >> >>> >>> >> >>> >>> <a href="mailto:wanproxy@lists.wanproxy.org">wanproxy@lists.wanproxy.org</a><br>
>>> >> >>> >>> >> >>> >>><br>
>>> >> >>> >>> >> >>> >>><br>
>>> >> >>> >>> >> >>> >>><br>
>>> >> >>> >>> >> >>> >>> <a href="http://lists.wanproxy.org/listinfo.cgi/wanproxy-wanproxy.org" target="_blank">http://lists.wanproxy.org/listinfo.cgi/wanproxy-wanproxy.org</a><br>
>>> >> >>> >>> >> >>> >><br>
>>> >> >>> >>> >> >>> >> Hi,<br>
>>> >> >>> >>> >> >>> >> I had that error with the 0.7.2 release. I'm using<br>
>>> >> >>> >>> >> >>> >> the<br>
>>> >> >>> >>> >> >>> >> latest<br>
>>> >> >>> >>> >> >>> >> code<br>
>>> >> >>> >>> >> >>> >> from subversion and I haven't seen the error again.<br>
>>> >> >>> >>> >> >>> >><br>
>>> >> >>> >>> >> >>> >> Regards,<br>
>>> >> >>> >>> >> >>> >> Diego<br>
>>> >> >>> >>> >> >>> >><br>
>>> >> >>> >>> >> >>> >> --<br>
>>> >> >>> >>> >> >>> >> Diego Woitasen<br>
>>> >> >>> >>> >> >><br>
>>> >> >>> >>> >> >><br>
>>> >> >>> >>> >> ><br>
>>> >> >>> >>> ><br>
>>> >> >>> >>> ><br>
>>> >> >>> >><br>
>>> >> >>> >><br>
>>> >> >>> ><br>
>>> >> >><br>
>>> >> >><br>
>>> >> ><br>
>>> ><br>
>>> ><br>
>><br>
>><br>
><br>
</div></div></blockquote></div><br></div></div>