Re: [NET] Errorhandling of "bad" FTP Servers

Yes, but apache commons sends first FEAT when i use autodetectUTF8(), which is imo wrong. The javadoc states that autodetectUTF8() has to be used before connect(), but i dont understand why. setAutodetectUTF8 only sets a flag which is consulted during connect; it does not send anything to the

Re: [NET] Errorhandling of "bad" FTP Servers

On 22 January 2017 at 16:37, Oliver Zemann wrote: > >> Please prefix the subject line with the Commons Component in future (as >> above) > > Sorry, next time i will do that. >> >> >> On 22 January 2017 at 09:12, Oliver Zemann >> wrote: >>> >>>

Re: [NET] Errorhandling of "bad" FTP Servers

Please prefix the subject line with the Commons Component in future (as above) Sorry, next time i will do that. On 22 January 2017 at 09:12, Oliver Zemann wrote: Hi, i would like to know how to handle FTP Servers that do not behave like they should (or behave

Re: [NET] Errorhandling of "bad" FTP Servers

Please prefix the subject line with the Commons Component in future (as above) On 22 January 2017 at 09:12, Oliver Zemann wrote: > Hi, i would like to know how to handle FTP Servers that do not behave like > they should (or behave different than most others). > For

Errorhandling of "bad" FTP Servers

Hi, i would like to know how to handle FTP Servers that do not behave like they should (or behave different than most others). For example, currently i would like to connect to one of those servers which sends " MODE Z" directly after a login (USER) which is interpreted wrong by apache commons