On Thu, 2013-01-10 at 00:13 +1100, David Bullock wrote: > Philippe, maybe in your environment now, it is not necessary to use a > SOCKS proxy to access the FTP server, and because of this, the SOCKS > proxy has not been configured to proxy for it. Does it fix your > problem if you tell XXE not to use a SOCKS proxy for the > (newly-addressed?) FTP server? > > The text "Malformed reply from SOCKS server" seems to come from the > bowels of the java.net.SocksSocketImpl class. As I read the code > there [1], it can be thrown any time a SOCKS server sends less data > than it ought to before closing the stream. > > cheers, David. >
Hi David, Thanks for pointing me to this; we comply with a global company Internet proxy policy, so XMLMind is simply configured to follow "System Settings". In these settings, we shall not use proxies to access our own servers (whether FTP, HTTP or other). Strangely enough: for ftp:// protocol, even though the host to which we upload belongs to the list of trusted hosts for which no proxy is needed, a SOCKS proxy is used however. This does not happen for other protocols ( HTTP, HTTPS, etc). So, many thanks again for your e-mail, which gives us a good workaround; we have now to understand where things go wrong... (can it come from flaws in the Java packages ?). Cheers, Phil.
-- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
