Re: Re: PUSH proxy !!

Thanks!! 
I fixed the bug in parsing logic and now getting the response from PUSH proxy e.g. status code 202.I have open a listener thread to listen on incoming request from firewalled peer.
I am getting GIV response in listener.Now i want to get download the actual file, for that , do i need to send another GET request with hash for example- 
                                            "GET {0} HTTP/1.1\r\n"
                                           + "Host: {1}:{2}\r\n"
                                           + "X-Node: {3}:{4}\r\n"
                                           + "User-Agent: HelloGnutella/1.0\r\n"
                                           + "Connection: Keep-Alive\r\n"
                                           + "Range: bytes=0-\r\n"
                                           + "X-Queue: 0.1\r\n"
                                           + "X-Features: queue/0.1\r\n"
                                           + "\r\n", url, ip, port, local_ip, local_port);

On the listener connection or need to send the GET resquest to PUSH proxy again after sending following  GET request
    GET /gnutella/pushproxy?ServerId=<PeerIdentifier> HTTP/1.1
X-Node: <IP address>:<Port>
Regards

[email protected] wrote:                                  Quoting rakesh <[email protected]> from ml.gnutella.dev-forum:
 :  I am trying to connect all the PUSH proxies coming in the Query hit but none of
 :them responding back :(.   Very few times they respond , say 1 out of 1,00,000.
 :  At TCP lavel SYN packet has sent to them but they are not acknowldging.
 :   
 :  Any pointers ?
 
 It's probably because they're long gone.  If you wait too much after the
 reception of the query hit, it is completely possible that the push proxies
 themselves have left the network.
 
 Or you got bogus information.
 
 Or your address parsing algorithm is broken and you're not reading
 endianness correctly.
 
 Raphael
 
     
                       

       
---------------------------------
Get the Yahoo! toolbar and be alerted to new email wherever you're surfing. 

[Non-text portions of this message have been removed]