[Pidgin] #7581: XMPP file transfer using file transfer proxy doesn't work

Pidgin trac at pidgin.im
Wed Nov 19 11:57:46 EST 2008


#7581: XMPP file transfer using file transfer proxy doesn't work
---------------------------------------------+------------------------------
 Reporter:  thenktor                         |        Owner:  deryni 
     Type:  defect                           |       Status:  pending
Milestone:                                   |    Component:  XMPP   
  Version:  2.5.2                            |   Resolution:         
 Keywords:  xmpp jabber file transfer proxy  |  
---------------------------------------------+------------------------------
Changes (by deryni):

  * status:  new => pending


Comment:

 Yes, the IPs presented from pidgin are local IPs but that shouldn't come
 into play yet. Things aren't getting that far.

 The stanzas that receive different responses are "<iq
 to="clericon at thenktor.dyndns.org/Home" type="set"
 id="id_R1CTAF0OIU763JMB"><query
 xmlns="http://jabber.org/protocol/bytestreams" mode="tcp"
 sid="R1CTAF0OIU763JMB"><streamhost host="87.176.86.209"
 jid="thenktor at thenktor.dyndns.org/Home-Gajim" port="28011" /><streamhost
 host="77.48.19.1" jid="proxy.netlab.cz" port="7777" /></query></iq>" from
 gajim and (the one you excerpted just now) "<iq type='set'
 id='purple7cf5832d' to='clericon at thenktor.dyndns.org/Home'><query
 xmlns='http://jabber.org/protocol/bytestreams'
 sid='purple7cf5832c'><streamhost jid='thenktor at thenktor.dyndns.org/Home'
 host='192.168.18.60' port='37437'/><streamhost
 jid='proxy.thenktor.dyndns.org' host='192.168.18.60'
 port='7777'/></query></iq>" from pidgin.

 The only substantive difference in the stanza themselves (and not the data
 they contain) is the lack of the mode attribute on the query element in
 the stanza sent from pidgin. If that is in fact the problem then whatever
 server or client is generating that error is broken. As according to
 [http://xmpp.org/extensions/xep-0065.html XEP-0065] the mode attribute is
 optional.

 The other possibility is that OpenFire is inspecting the offered
 streamhosts and informing you that it can't possibly use any of them
 (something it definitely should not be doing and is decidedly broken if it
 is). If you manually added your proxy server in your account settings for
 that account could you try setting the netlab proxy instead and seeing if
 file transfers from pidgin work then? If they do I'm going to go back to
 this being a horrible OpenFire bug.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/7581#comment:6>
Pidgin <http://pidgin.im>
Pidgin


More information about the Tracker mailing list