Bug #97608 for Net-FTPSSL: Bugreport Net::FTPSSL v0.24

Tue Jul 29 18:52:18 2014 kallmeie [...] fim.uni-passau.de - Ticket created

Subject:	Bugreport Net::FTPSSL v0.24
Date:	Wed, 30 Jul 2014 00:51:56 +0200
To:	bug-Net-FTPSSL [...] rt.cpan.org
From:	Fabian Kallmeier <kallmeie [...] fim.uni-passau.de>

Message body is not shown because it is too large.

Wed Jul 30 00:22:32 2014 CLEACH [...] cpan.org - Correspondence added

Hi Fabian, Thank you for writing. I'm always interested in hearing feedback about my module. Your main issue seems to be a time out issue with my module. And that happened to be the major focus of my last release. Before v0.24, the Timeout option really didn't do anything. The underlying code my class inherited from said it did something with it, but it turned out it really ignored the flag as far as I could tell. So I finally had to implement a timeout myself to fix another issue using the existing Timeout option. So have you tried increasing "Timeout => 20" to something larger to see if it fixed your issue? The Timeout values defaults to 120. A better test script would have been: $site = Net::FTPSSL->new("<IP>", Port => <PORT>, Croak => 1, Debug=>1, DebugLogFile => "myLog.txt") $site->login("<USERNAME>", "<PASSWORD>"); $site->quit(); The "Croak" option handles the "or die" for you. So you don't have to put that into your code. I also left off Timeout on purpose. With this test script you could have sent me the entire log file "myLog.txt" as an attachment instead of mixing it in with your problem description. Making it much easier to read & figure out your problem. Could you rerun the test with v0.24 again & send me the "myLog.txt" log file? Now onto Section # 2. There was a bug in your test script, which was why last_message() returned the message for "help" instead of "feat". There was a reason I didn't document command(), which you used incorrectly. You could have gotten the results you wanted by calling $site->quot("feat");, which was documented. Try: perldoc Net::FTPSSL for the built in documentation on this module. It documents every method that is safe to use & details the available options to "new()". You have to assume any method or option not documented I feel safe to change between releases. Next, did increasing the buffer size from 4096 to 8192 fix your problem? If it did, I'm assuming you just hid it until something even bigger comes along. So can I have a login on your FTP server to test out some code? I'll give you my personal email so you can avoid posting the information if you can. As to the warnings, I'll look into it. Your patch gave me ideas on how to fix it. But a separate log file will help me confirm it. As for the status code being split between two lines, that is the behavior of your server. I've run into that issue before and I think my code handles it quite well. I'm very leery of modifying the response to put it back on one line since that will tend to hide issues in future tickets. But again a log file generated as an attachment will help me confirm this or if its a similar type of problem I'm not handling. Once I get your full log file, if I can't test against your server I can send you a beta of the next release to see if it helps any. It has a couple of new features to help with reporting on issues that I'm still trying to work out. But I'll want to take a stab at fixing the warning issue before I give out a new beta. I'm looking forward to hearing back from you. Curtis On Tue Jul 29 18:52:18 2014, kallmeie@fim.uni-passau.de wrote: Show quoted text

> Hey there, > > first of all. I want to thank you for all your work. I already use > this > module for a long time and I really appretiate it! > > Recently, I ran into two issues. First of all, some details to my > system: > > OS: Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u1 x86_64 GNU/Linux > Perl: This is perl 5, version 14, subversion 2 (v5.14.2) built for > x86_64-linux-gnu-thread-multi > Module: Net::FTPSSL v0.24 > > *1. issue:* > > Since the update from 0.23 to 0.24, I cannot connect to one of my ftp > servers any more. The daemon is drftpd. When I turn on debug mode, It > stopps while printing the welcome message. (which is pretty long) I > initialize the object like this: > > $site = Net::FTPSSL->new("<IP>", Port => <PORT>, Timeout => 20, Croak => 1) > or die $Net::FTPSSL::ERRSTR; > $site->login("<USERNAME>", "<PASSWORD>") > or die $Net::FTPSSL::ERRSTR; > > The script quits with the error: > > Timed out waiting for a response! > at test.pl line 24 > > Line 24 is the line where I try to login to the server, not where I > initialize the object. > > <<+ 214 The HELP command is supported.

> >>> feat

> 214 The HELP command is supported. > > As you can see, there are several things that go wrong here. > > 1. Same problem as with the drftpd, the long welcome message is split > in > the middle of some lines. > 2. Sometimes, there is just the first digit of the response code or > the > first character of some commands in one line (2 of 211, A of ABORT, M > of > Mode, R of RNTO, ...) > 3. There are empty lines in the "feat"-command, if I am right, thats > why > there is the error message "Use of uninitialized value ..." > 4. print $site->last_message () in my script should print the response > of the "feat"-command, instead, it just prints the last line ("214 The > HELP command is supported.") > > I also tried to solve theese problems on my own. Here is a diff of the > latest module version and my changes: > > 2398a2399,2400

> > next if ( $line eq "" ); > >

> 2627c2629,2630 > < my $read = sysread( $self, $data, 4096); > ---

> > # my $read = sysread( $self, $data, 4096); > > my $read = sysread( $self, $data, 8196);

> 2662a2666,2667

> > my $addCR = 1; > >

> 2667a2673

> > $addCR = 0 if (length ($code) < 3 && $sep eq "" and $desc

> eq ""); > 2681d2686 > < > 2686c2691,2693 > < ${*$self}{last_ftp_msg} .= "\n"; # Restore the > internal <CR>. > ---

> > if ($addCR == 1) { > > ${*$self}{last_ftp_msg} .= "\n"; # Restore the

> internal <CR>.

> > }

> > 2398a2399,2400 <-- The "Use of uninitialized value ..." errors where > gone, because empty lines are ignored > 2627c2629,2630 <-- Increasing the length value > > All other changes solved the issue, that some responses with a > response > code where split after the first digit, not for the debug messages but > for the output of $site->last_message (). > > As I could see, the subroutine response has a lot of special cases > because the differend ftpds seem to handle the responses differently. > I > don't know if you are interested in supporting another ftp daemon. If > I'm right, my changes just affected lines which were added to fix the > bug # 73115 so hopefully, they don't effect other ftp daemons. If you > don't want to add more special cases, perhaps you could check if your > test cases still work with my changes? > > Many thanks in advance for reading this, I hope this mail is not a > complete mess :-) If you have any questions, need more details, more > debug outputs or something else, don't hesitate to ask! > > Best wishes > > Fabian Kallmeier

Wed Jul 30 00:22:33 2014 The RT System itself - Status changed from 'new' to 'open'

Wed Jul 30 00:22:33 2014 CLEACH [...] cpan.org - Fixed in 0.24 added

Wed Jul 30 00:26:42 2014 CLEACH [...] cpan.org - Fixed in 0.24 deleted

Wed Jul 30 00:26:42 2014 CLEACH [...] cpan.org - Broken in 0.24 added

Wed Jul 30 01:49:08 2014 CLEACH [...] cpan.org - Correspondence added

Hi again, I've been reviewing my code a bit closer for the warnings reported & I'd like to propose this as your new test program to run against v0.24: $site = Net::FTPSSL->new("<IP>", Port => <PORT>, Croak => 1, Debug=>1, DebugLogFile => "myLog.txt") $site->login("<USERNAME>", "<PASSWORD>"); $f=$site->_feat(); $h=$site->_help(); $site->quit(); open (LOG, ">>", "myLog.txt"); print LOG "\n\n"; print LOG "Help: (", join ("), (", %{$h}), ")\n\n"; print LOG "Feat: (", join ("), (", %{$f}), ")\n"; close (LOG); This will tell me how messy the server returns this info that I parse internally. I probably have more to fix than I initially thought for things to work properly on your server. Running it against v0.23 probably wouldn't hurt either. So that I'd get the Help & Feat lines in logs for that version as well. I have a strong suspicion that the supported() function isn't really working well with your servers. Curtis On Wed Jul 30 00:22:32 2014, CLEACH wrote: Show quoted text

> Hi Fabian, > > Thank you for writing. I'm always interested in hearing feedback > about my module. > > Your main issue seems to be a time out issue with my module. And that > happened to be the major focus of my last release. Before v0.24, the > Timeout option really didn't do anything. The underlying code my > class inherited from said it did something with it, but it turned out > it really ignored the flag as far as I could tell. So I finally had > to implement a timeout myself to fix another issue using the existing > Timeout option. > > So have you tried increasing "Timeout => 20" to something larger to > see if it fixed your issue? The Timeout values defaults to 120. > > A better test script would have been: > $site = Net::FTPSSL->new("<IP>", Port => <PORT>, Croak => 1, Debug=>1, > DebugLogFile => "myLog.txt") > $site->login("<USERNAME>", "<PASSWORD>"); > $site->quit(); > > The "Croak" option handles the "or die" for you. So you don't have to > put that into your code. I also left off Timeout on purpose. > > With this test script you could have sent me the entire log file > "myLog.txt" as an attachment instead of mixing it in with your problem > description. Making it much easier to read & figure out your problem. > > Could you rerun the test with v0.24 again & send me the "myLog.txt" > log file? > > Now onto Section # 2. There was a bug in your test script, which was > why last_message() returned the message for "help" instead of "feat". > There was a reason I didn't document command(), which you used > incorrectly. You could have gotten the results you wanted by calling > $site->quot("feat");, which was documented. Try: perldoc Net::FTPSSL > for the built in documentation on this module. It documents every > method that is safe to use & details the available options to "new()". > You have to assume any method or option not documented I feel safe to > change between releases. > > Next, did increasing the buffer size from 4096 to 8192 fix your > problem? If it did, I'm assuming you just hid it until something even > bigger comes along. > > So can I have a login on your FTP server to test out some code? I'll > give you my personal email so you can avoid posting the information if > you can. > > As to the warnings, I'll look into it. Your patch gave me ideas on > how to fix it. But a separate log file will help me confirm it. > > As for the status code being split between two lines, that is the > behavior of your server. I've run into that issue before and I think > my code handles it quite well. I'm very leery of modifying the > response to put it back on one line since that will tend to hide > issues in future tickets. But again a log file generated as an > attachment will help me confirm this or if its a similar type of > problem I'm not handling. > > Once I get your full log file, if I can't test against your server I > can send you a beta of the next release to see if it helps any. It > has a couple of new features to help with reporting on issues that I'm > still trying to work out. But I'll want to take a stab at fixing the > warning issue before I give out a new beta. > > I'm looking forward to hearing back from you. > > Curtis > > On Tue Jul 29 18:52:18 2014, kallmeie@fim.uni-passau.de wrote:

> > Hey there, > > > > first of all. I want to thank you for all your work. I already use > > this > > module for a long time and I really appretiate it! > > > > Recently, I ran into two issues. First of all, some details to my > > system: > > > > OS: Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u1 x86_64 > > GNU/Linux > > Perl: This is perl 5, version 14, subversion 2 (v5.14.2) built for > > x86_64-linux-gnu-thread-multi > > Module: Net::FTPSSL v0.24 > > > > *1. issue:* > > > > Since the update from 0.23 to 0.24, I cannot connect to one of my ftp > > servers any more. The daemon is drftpd. When I turn on debug mode, It > > stopps while printing the welcome message. (which is pretty long) I > > initialize the object like this: > > > > $site = Net::FTPSSL->new("<IP>", Port => <PORT>, Timeout => 20, Croak > > => 1) > > or die $Net::FTPSSL::ERRSTR; > > $site->login("<USERNAME>", "<PASSWORD>") > > or die $Net::FTPSSL::ERRSTR; > > > > The script quits with the error: > > > > Timed out waiting for a response! > > at test.pl line 24 > > > > Line 24 is the line where I try to login to the server, not where I > > initialize the object. > > > > <<+ 214 The HELP command is supported.

> > >>> feat

> > 214 The HELP command is supported. > > > > As you can see, there are several things that go wrong here. > > > > 1. Same problem as with the drftpd, the long welcome message is split > > in > > the middle of some lines. > > 2. Sometimes, there is just the first digit of the response code or > > the > > first character of some commands in one line (2 of 211, A of ABORT, M > > of > > Mode, R of RNTO, ...) > > 3. There are empty lines in the "feat"-command, if I am right, thats > > why > > there is the error message "Use of uninitialized value ..." > > 4. print $site->last_message () in my script should print the > > response > > of the "feat"-command, instead, it just prints the last line ("214 > > The > > HELP command is supported.") > > > > I also tried to solve theese problems on my own. Here is a diff of > > the > > latest module version and my changes: > > > > 2398a2399,2400

> > > next if ( $line eq "" ); > > >

> > 2627c2629,2630 > > < my $read = sysread( $self, $data, 4096); > > ---

> > > # my $read = sysread( $self, $data, 4096); > > > my $read = sysread( $self, $data, 8196);

> > 2662a2666,2667

> > > my $addCR = 1; > > >

> > 2667a2673

> > > $addCR = 0 if (length ($code) < 3 && $sep eq "" and $desc

> > eq ""); > > 2681d2686 > > < > > 2686c2691,2693 > > < ${*$self}{last_ftp_msg} .= "\n"; # Restore the > > internal <CR>. > > ---

> > > if ($addCR == 1) { > > > ${*$self}{last_ftp_msg} .= "\n"; # Restore the

> > internal <CR>.

> > > }

> > > > 2398a2399,2400 <-- The "Use of uninitialized value ..." errors where > > gone, because empty lines are ignored > > 2627c2629,2630 <-- Increasing the length value > > > > All other changes solved the issue, that some responses with a > > response > > code where split after the first digit, not for the debug messages > > but > > for the output of $site->last_message (). > > > > As I could see, the subroutine response has a lot of special cases > > because the differend ftpds seem to handle the responses differently. > > I > > don't know if you are interested in supporting another ftp daemon. If > > I'm right, my changes just affected lines which were added to fix the > > bug # 73115 so hopefully, they don't effect other ftp daemons. If you > > don't want to add more special cases, perhaps you could check if your > > test cases still work with my changes? > > > > Many thanks in advance for reading this, I hope this mail is not a > > complete mess :-) If you have any questions, need more details, more > > debug outputs or something else, don't hesitate to ask! > > > > Best wishes > > > > Fabian Kallmeier

Wed Jul 30 09:27:52 2014 kallmeie [...] fim.uni-passau.de - Correspondence added

Subject:	[rt.cpan.org #97608]
Date:	Wed, 30 Jul 2014 15:27:33 +0200
To:	bug-Net-FTPSSL [...] rt.cpan.org
From:	Fabian Kallmeier <kallmeie [...] fim.uni-passau.de>

Hey Curtis, thank you for replying so fast. Sorry for the confusing message, lets bring some order in it :-) *1. Timeout issue* I tried increasing the timeout by not defining it in new and therefore using the default value of 120, but still it just stopps while printing the welcome message and after 120 seconds, it quits saying "Timed out waiting for a response!". I attached timeout.log to this email which is the debug output of the following code: my $site = Net::FTPSSL->new("<IP>", Port => <PORT>, Croak => 1, Debug=>1, DebugLogFile => "timeout.txt"); $site->login("<USERNAME>", "<PASSWORD>"); $site->quit(); Increasing the buffer size solved this issue! Im afraid I cannot give you access to this server, because its not my own one. *2. Cubnc issue* By using $site->quot("feat"); I get the result of the whole feat command, thank you for the hint! Of course there still is the problem with the "\n" after the first digit of most of the response codes. I attached cubnc.log, which is the ouput of the following code: my $site = Net::FTPSSL->new("<IP>", Port => <PORT>, Croak => 1, Debug => 1, DebugLogFile => "cubnc.txt"); $site->login("<USERNAME>", "<PASSWORD>"); $site->quit(); Last but not least, I ran the code you postet in your second response. The result is in cubnc_ext_v0.23.txt and cubnc_ext_v0.24.txt. They just differ in some ssl settings and in 0.23, there is one "\n" more in the welcome message than there is in 0.24. If it helps, I could give you an account for the cubnc server. Just give me your email address and I'll send you the login details. Best regards Fabian

Message body is not shown because sender requested not to inline it.

Sat Aug 02 13:19:12 2014 CLEACH [...] cpan.org - Correspondence added

Hi Fabian, Sorry for the delay, but the paying job got in the way. Please do send my your info to CLEACH@cpan.com I'm going to put some debug statements into a beta for you to use in testing out the problem on your private server. I'm not sure yet, if I'm going to increase the buffer size to hide the problem or use a Timeout of -1 to turn off the timeout logic. But I have to compare your works/doesn't work logs to see if it will do any good. I'll see if I can get you a beta by Monday. Curtis On Wed Jul 30 09:27:52 2014, kallmeie@fim.uni-passau.de wrote: Show quoted text

> Hey Curtis, > > thank you for replying so fast. Sorry for the confusing message, lets > bring some order in it :-) > > *1. Timeout issue* > > I tried increasing the timeout by not defining it in new and therefore > using the default value of 120, but still it just stopps while printing > the welcome message and after 120 seconds, it quits saying "Timed out > waiting for a response!". I attached timeout.log to this email which is > the debug output of the following code: > > my $site = Net::FTPSSL->new("<IP>", Port => <PORT>, Croak => 1, > Debug=>1, DebugLogFile => "timeout.txt"); > $site->login("<USERNAME>", "<PASSWORD>"); > $site->quit(); > > Increasing the buffer size solved this issue! Im afraid I cannot give > you access to this server, because its not my own one. > > *2. Cubnc issue* > > By using $site->quot("feat"); I get the result of the whole feat > command, thank you for the hint! Of course there still is the problem > with the "\n" after the first digit of most of the response codes. > > I attached cubnc.log, which is the ouput of the following code: > > my $site = Net::FTPSSL->new("<IP>", Port => <PORT>, Croak => 1, Debug => > 1, DebugLogFile => "cubnc.txt"); > $site->login("<USERNAME>", "<PASSWORD>"); > $site->quit(); > > Last but not least, I ran the code you postet in your second response. > The result is in cubnc_ext_v0.23.txt and cubnc_ext_v0.24.txt. They just > differ in some ssl settings and in 0.23, there is one "\n" more in the > welcome message than there is in 0.24. > > If it helps, I could give you an account for the cubnc server. Just give > me your email address and I'll send you the login details. > > Best regards > > Fabian

Sun Aug 03 03:24:06 2014 cleach [...] Caesars.com - Correspondence added

Subject:	RE: [rt.cpan.org #97608]
Date:	Sun, 3 Aug 2014 07:23:51 +0000
To:	"bug-Net-FTPSSL [...] rt.cpan.org" <bug-Net-FTPSSL [...] rt.cpan.org>
From:	Curtis Leach <cleach [...] Caesars.com>

Fabian, I had a typo in my email address. Use cleach@CPAN.org I don't have access to a server that's having those issues. So I want to take you up on your offer so that I can fully debug this module for this problem while I have the chance. As to your other server that you can't grant me access to, attached is my beta to run against it. Try the following test program my $ftp = Net::FTPSSL->new ("server", Croak=>1, Debug=>1, DebugLogFile=>"myLog.txt"); $ftp->trapWarn(); # New function in the beta. $ftp->login (user, pwd); $ftp->quit(); Then return the log file for me to review, even if it works. I'm hoping to catch the error you are encountering In the logs. I really don't want to just increase the buffer size until I have a chance to understand why it's failing. Especially when the vast majority of the time not much data is returned on the command channel. Curtis

Message body is not shown because sender requested not to inline it.

Wed Aug 06 12:25:23 2014 CLEACH [...] cpan.org - Correspondence added

Hi Fabian, Did you get my beta? I would also like access to the server that's returning extra line breaks. Curtis On Sat Aug 02 13:19:12 2014, CLEACH wrote: Show quoted text

> Hi Fabian, > > Sorry for the delay, but the paying job got in the way. > > Please do send my your info to CLEACH@cpan.org > > I'm going to put some debug statements into a beta for you to use in > testing out the problem on your private server. I'm not sure yet, if > I'm going to increase the buffer size to hide the problem or use a > Timeout of -1 to turn off the timeout logic. But I have to compare > your works/doesn't work logs to see if it will do any good. > > I'll see if I can get you a beta by Monday. > > Curtis > > On Wed Jul 30 09:27:52 2014, kallmeie@fim.uni-passau.de wrote:

> > Hey Curtis, > > > > thank you for replying so fast. Sorry for the confusing message, lets > > bring some order in it :-) > > > > *1. Timeout issue* > > > > I tried increasing the timeout by not defining it in new and > > therefore > > using the default value of 120, but still it just stopps while > > printing > > the welcome message and after 120 seconds, it quits saying "Timed out > > waiting for a response!". I attached timeout.log to this email which > > is > > the debug output of the following code: > > > > my $site = Net::FTPSSL->new("<IP>", Port => <PORT>, Croak => 1, > > Debug=>1, DebugLogFile => "timeout.txt"); > > $site->login("<USERNAME>", "<PASSWORD>"); > > $site->quit(); > > > > Increasing the buffer size solved this issue! Im afraid I cannot give > > you access to this server, because its not my own one. > > > > *2. Cubnc issue* > > > > By using $site->quot("feat"); I get the result of the whole feat > > command, thank you for the hint! Of course there still is the problem > > with the "\n" after the first digit of most of the response codes. > > > > I attached cubnc.log, which is the ouput of the following code: > > > > my $site = Net::FTPSSL->new("<IP>", Port => <PORT>, Croak => 1, Debug > > => > > 1, DebugLogFile => "cubnc.txt"); > > $site->login("<USERNAME>", "<PASSWORD>"); > > $site->quit(); > > > > Last but not least, I ran the code you postet in your second > > response. > > The result is in cubnc_ext_v0.23.txt and cubnc_ext_v0.24.txt. They > > just > > differ in some ssl settings and in 0.23, there is one "\n" more in > > the > > welcome message than there is in 0.24. > > > > If it helps, I could give you an account for the cubnc server. Just > > give > > me your email address and I'll send you the login details. > > > > Best regards > > > > Fabian

Tue Aug 19 19:52:46 2014 CLEACH [...] cpan.org - Correspondence added

Hi Fabian, I never heard back from you about my access or my previous beta I sent to you. But in the mean time I did verify there was a couple of minor bugs in the response() code that required me to completely redesign how it worked. It was just getting too convoluted with all the past bug fixes to put any new patches into it. It was easier just to rewrite it from scratch again. I think it was the bug that was inserting the extra returns into the message. Not something strange that your server was doing. But I'd like to review it by testing it against your server to be sure. I also think I know why the timeout logic wasn't working for you. So that needs to be tested as well. Let me know if you are willing & I'll send you another beta. Otherwise I'll just upload my changes and call it a day in a week or so. I still have some testing to do on my end to make sure I didn't introduce any other problems with the redesign. Curtis On Wed Aug 06 12:25:23 2014, CLEACH wrote: Show quoted text

> Hi Fabian, > > Did you get my beta? > > I would also like access to the server that's returning extra line breaks. > > Curtis > > On Sat Aug 02 13:19:12 2014, CLEACH wrote:

> > Hi Fabian, > > > > Sorry for the delay, but the paying job got in the way. > > > > Please do send my your info to CLEACH@cpan.org > > > > I'm going to put some debug statements into a beta for you to use in > > testing out the problem on your private server. I'm not sure yet, if > > I'm going to increase the buffer size to hide the problem or use a > > Timeout of -1 to turn off the timeout logic. But I have to compare > > your works/doesn't work logs to see if it will do any good. > > > > I'll see if I can get you a beta by Monday. > > > > Curtis > > > > On Wed Jul 30 09:27:52 2014, kallmeie@fim.uni-passau.de wrote:

> > > Hey Curtis, > > > > > > thank you for replying so fast. Sorry for the confusing message, lets > > > bring some order in it :-) > > > > > > *1. Timeout issue* > > > > > > I tried increasing the timeout by not defining it in new and > > > therefore > > > using the default value of 120, but still it just stopps while > > > printing > > > the welcome message and after 120 seconds, it quits saying "Timed out > > > waiting for a response!". I attached timeout.log to this email which > > > is > > > the debug output of the following code: > > > > > > my $site = Net::FTPSSL->new("<IP>", Port => <PORT>, Croak => 1, > > > Debug=>1, DebugLogFile => "timeout.txt"); > > > $site->login("<USERNAME>", "<PASSWORD>"); > > > $site->quit(); > > > > > > Increasing the buffer size solved this issue! Im afraid I cannot give > > > you access to this server, because its not my own one. > > > > > > *2. Cubnc issue* > > > > > > By using $site->quot("feat"); I get the result of the whole feat > > > command, thank you for the hint! Of course there still is the problem > > > with the "\n" after the first digit of most of the response codes. > > > > > > I attached cubnc.log, which is the ouput of the following code: > > > > > > my $site = Net::FTPSSL->new("<IP>", Port => <PORT>, Croak => 1, Debug > > > => > > > 1, DebugLogFile => "cubnc.txt"); > > > $site->login("<USERNAME>", "<PASSWORD>"); > > > $site->quit(); > > > > > > Last but not least, I ran the code you postet in your second > > > response. > > > The result is in cubnc_ext_v0.23.txt and cubnc_ext_v0.24.txt. They > > > just > > > differ in some ssl settings and in 0.23, there is one "\n" more in > > > the > > > welcome message than there is in 0.24. > > > > > > If it helps, I could give you an account for the cubnc server. Just > > > give > > > me your email address and I'll send you the login details. > > > > > > Best regards > > > > > > Fabian

> >

Fri Sep 05 20:31:36 2014 CLEACH [...] cpan.org - Correspondence added

Hi Fabian, I've finished making the changes that should fix your problem and uploaded it as an official release (v0.25) It should be available in an hour or so. I think I figured out a way to get any FTPS server to behave the way yours did. So I was able to do extensive testing of my changes. This release should fix all the issues you reported in your bug report. But I'd appreciate it if you tried it out & got back to me with the results. If I don't hear back from you by the end of next week, I'll assume all is OK and close this ticket. If for some reason it doesn't work for you, I'll need two log files generated. The 1st using Debug=>1 & the 2nd using Debug=>99. With both logs generated by the same test code that demonstrates the problem. The 99 option just generates supper verbose log files. Curtis On Tue Aug 19 19:52:46 2014, CLEACH wrote: Show quoted text

> Hi Fabian, > > I never heard back from you about my access or my previous beta I sent > to you. > > But in the mean time I did verify there was a couple of minor bugs in > the response() code that required me to completely redesign how it > worked. It was just getting too convoluted with all the past bug > fixes to put any new patches into it. It was easier just to rewrite > it from scratch again. > > I think it was the bug that was inserting the extra returns into the > message. Not something strange that your server was doing. But I'd > like to review it by testing it against your server to be sure. > > I also think I know why the timeout logic wasn't working for you. So > that needs to be tested as well. > > Let me know if you are willing & I'll send you another beta. > Otherwise I'll just upload my changes and call it a day in a week or > so. I still have some testing to do on my end to make sure I didn't > introduce any other problems with the redesign. > > Curtis > > On Wed Aug 06 12:25:23 2014, CLEACH wrote:

> > Hi Fabian, > > > > Did you get my beta? > > > > I would also like access to the server that's returning extra line > > breaks. > > > > Curtis > > > > On Sat Aug 02 13:19:12 2014, CLEACH wrote:

> > > Hi Fabian, > > > > > > Sorry for the delay, but the paying job got in the way. > > > > > > Please do send my your info to CLEACH@cpan.org > > > > > > I'm going to put some debug statements into a beta for you to use > > > in > > > testing out the problem on your private server. I'm not sure yet, > > > if > > > I'm going to increase the buffer size to hide the problem or use a > > > Timeout of -1 to turn off the timeout logic. But I have to compare > > > your works/doesn't work logs to see if it will do any good. > > > > > > I'll see if I can get you a beta by Monday. > > > > > > Curtis > > > > > > On Wed Jul 30 09:27:52 2014, kallmeie@fim.uni-passau.de wrote:

> > > > Hey Curtis, > > > > > > > > thank you for replying so fast. Sorry for the confusing message, > > > > lets > > > > bring some order in it :-) > > > > > > > > *1. Timeout issue* > > > > > > > > I tried increasing the timeout by not defining it in new and > > > > therefore > > > > using the default value of 120, but still it just stopps while > > > > printing > > > > the welcome message and after 120 seconds, it quits saying "Timed > > > > out > > > > waiting for a response!". I attached timeout.log to this email > > > > which > > > > is > > > > the debug output of the following code: > > > > > > > > my $site = Net::FTPSSL->new("<IP>", Port => <PORT>, Croak => 1, > > > > Debug=>1, DebugLogFile => "timeout.txt"); > > > > $site->login("<USERNAME>", "<PASSWORD>"); > > > > $site->quit(); > > > > > > > > Increasing the buffer size solved this issue! Im afraid I cannot > > > > give > > > > you access to this server, because its not my own one. > > > > > > > > *2. Cubnc issue* > > > > > > > > By using $site->quot("feat"); I get the result of the whole feat > > > > command, thank you for the hint! Of course there still is the > > > > problem > > > > with the "\n" after the first digit of most of the response > > > > codes. > > > > > > > > I attached cubnc.log, which is the ouput of the following code: > > > > > > > > my $site = Net::FTPSSL->new("<IP>", Port => <PORT>, Croak => 1, > > > > Debug > > > > => > > > > 1, DebugLogFile => "cubnc.txt"); > > > > $site->login("<USERNAME>", "<PASSWORD>"); > > > > $site->quit(); > > > > > > > > Last but not least, I ran the code you postet in your second > > > > response. > > > > The result is in cubnc_ext_v0.23.txt and cubnc_ext_v0.24.txt. > > > > They > > > > just > > > > differ in some ssl settings and in 0.23, there is one "\n" more > > > > in > > > > the > > > > welcome message than there is in 0.24. > > > > > > > > If it helps, I could give you an account for the cubnc server. > > > > Just > > > > give > > > > me your email address and I'll send you the login details. > > > > > > > > Best regards > > > > > > > > Fabian

> > > >

Mon Sep 08 20:21:36 2014 CLEACH [...] cpan.org - Fixed in 0.25 added

Mon Sep 08 20:21:36 2014 CLEACH [...] cpan.org - Severity Important added

Thu Sep 18 19:00:41 2014 CLEACH [...] cpan.org - Status changed from 'open' to 'resolved'