[Cyberduck-trac] [Cyberduck] #2017: Why does Cyberduck keep trying the FEAT command after receiving "500 'FEAT': command not understood"?

[Cyberduck]

#2017: Why does Cyberduck keep trying the FEAT command after receiving "500
'FEAT': command not understood"?
------------------------------------+---------------------------------------
 Reporter:  George_OConnor at USA.net  |        Owner:  dkocher
     Type:  defect                  |       Status:  closed 
 Priority:  normal                  |    Milestone:  3.0    
Component:  ftp                     |      Version:  2.8.5  
 Severity:  normal                  |   Resolution:  fixed  
 Keywords:                          |  
------------------------------------+---------------------------------------
Changes (by dkocher):

  * status:  new => closed
  * resolution:  => fixed
  * component:  core => ftp
  * milestone:  3.1 => 3.0

Old description:

> Why does Cyberduck keep trying the FEAT command after receiving "500
> 'FEAT': command not understood"?  This just seems like a waste of
> bandwidth.

New description:

 Why does Cyberduck keep trying the FEAT command after receiving
 "{{{500 'FEAT': command not understood}}}"?  This just seems like a waste
 of bandwidth.

Comment:

 In r3940.

-- 
Ticket URL: <http://trac.cyberduck.ch/ticket/2017#comment:1>
Cyberduck <http://cyberduck.ch>
FTP and SFTP Browser for Mac OS X.