[issue9601] ftplib should accept 250 on MKD

Giampaolo Rodola' added the comment: This is now fixed in r84288. -- assignee: -> giampaolo.rodola resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue9601] ftplib should accept 250 on MKD

Giampaolo Rodola' added the comment: Given Antoine comment and the link referencing bzr issue I agree we should fix this now. A patch including tests for parse257 function is in attachment. The exception is now raised only if the response code doesn't fall in the 2xx category; for responses !=

[issue9601] ftplib should accept 250 on MKD

alphablue52 added the comment: Jep I also discovered it by using Bazaar, but apparently it goes down to the ftplib. The bazaar fix works, and here is the response of strato.com (I use bash ftp): ftp> open ftp.strato.com Connected to ftp.strato.com. 220 Speak friend, and enter Name (ftp.strato

[issue9601] ftplib should accept 250 on MKD

Antoine Pitrou added the comment: Well, given that both replies (expected and actual) are in the 25x category, and that (according to the RFC) “the third digit gives a finer gradation of meaning in each of the function categories, specified by the second digit”, perhaps practicality beats pur

[issue9601] ftplib should accept 250 on MKD

Giampaolo Rodola' added the comment: What IIS version are we talking about? Could you please paste the complete response string other than just the code? I'm asking this because 257 response is supposed to include the name of the created directory. Personally I don't like to include workaround

[issue9601] ftplib should accept 250 on MKD

alphablue52 added the comment: 250 is an invalid response to MKD. M$ Windows Server 2003 does it anyways. M$ Windows Server is a rather common OS, and there are people like me how have to live with this. Maybe it should put this into the following words: "Please make ftplib usuable with M$ Win

[issue9601] ftplib should accept 250 on MKD

Giampaolo Rodola' added the comment: Where exactly RFC-959 states that 250 is a valid response code for MKD? Chapter 5.4 reports the following response codes: MKD 257 500, 501, 502, 421, 530, 550 -- ___ Python tracker

[issue9601] ftplib should accept 250 on MKD

alphablue52 added the comment: Yes. If you send a "MKD" than Windows Server responses "250", and ftplib generates an Error. -- ___ Python tracker ___ ___

[issue9601] ftplib should accept 250 on MKD

Giampaolo Rodola' added the comment: > The server responses 250 instead of 257 (which would be correct according to > RFC959, ftp) In response to what command? MKD? And what do you mean by "tolerate"? -- ___ Python tracker

[issue9601] ftplib should accept 250 on MKD

Changes by Antoine Pitrou : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue9601] ftplib should accept 250 on MKD

Eric Smith added the comment: Since this is a feature request, it could only be added to 3.2, not the other versions. -- nosy: +eric.smith type: behavior -> feature request versions: -Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 3.3 ___ P

[issue9601] ftplib should accept 250 on MKD

Changes by alphablue52 : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue9601] ftplib should accept 250 on MKD

New submission from alphablue52 : I try to use ftplib for a Webspace running on a Windows Server machine. The server responses 250 instead of 257 (which would be correct according to RFC959, ftp) It would be nice if ftplib could also tolerate the 250 "Requested file ation okay, completed" code