After hours of debugging, i realised that Openfire doesn’t always act as a proxy for file transfers( although i enabled it), more specifically, it doesn’t act as a proxy when the clients (sender and receiver) are in the same network. Is there a way i can force openfire to act always as a proxy for file transfers?
Thank you
normally it is up to client whether it needs proxy or not
actually, the openfire server initiates the transfer, and tells the client what to do next (i think)…
but if you are true, then maybe you know a method of forcing Spark to use the openfire server as proxy…
Hi. First of all I have to admit that my answer was based purely on “I-have-never-seen-it-done-other-way” thing and I’m absolutely no expert in xmpp - I started playing with xmpp-related programming only a week ago. But, again, according to this: http://www.xmpp.org/extensions/xep-0065.html#usecase first shot is always to try connect directly. If you take a look here http://www.xmpp.org/extensions/xep-0065.html#proto-inform IMO it turns out that cutting out clients own ip:port from the query should be enough to force transfer via proxy, so this can be done on server side or on (initiator)client side. Other thing is why in the world do you need it to be done this way?
Oh, thanks for the links.
The reason i want the server to always act as a proxy is because i’m working on improving the audit plugin (actually creating a new one) and i’m trying to intercept the files also.