#92 Firewalled Shareaza servers should emit an X-Push-Proxy header in their HTTP replies

[Raphael Manfredi]

According to the push-proxy specifications:

4.2 In HTTP Handshakes

During a HTTP session a firewalled servent MUST tell its downloader the most up-to-date proxy information. This is communicated via the new HTTP Header 'X-Push-Proxy', whose format is a comma delineated list of DottedIPAddress:Port combinations. A servent that receives this list MUST immediately replace its known list of proxy servers for the firewalled servent with this updated list.

Apparently Shareaza is not complying to this point in the push-proxy specifications. Setting priority to "major" due to non-compliance.

The server-side support should be trivial to implement. You are free to ignore this information published by other servents if you so desire.

[raspopov]

• priority changed from major to trivial
• type changed from defect to enhancement

[OldDeath]

• component set to Gnutella 1

[kevogod]

• status changed from new to assigned
• cc kevogod added
• priority changed from trivial to major
• milestone set to 2.5.6.0
• owner set to raspopov
• type changed from enhancement to defect

I argue this is a defect as it is not in compliance. Also, it would be very beneficial for Shareaza users who use Gnutella. Please do not change this back to enhancement/trivial unless you have a good explanation.

More information can be found at: http://gtk-gnutella.svn.sourceforge.net/svnroot/gtk-gnutella/trunk/gtk-gnutella/doc/gnutella/push_proxy