Same skip seems to not work anymore

In the previous versions of FlashFXP when I had skip transfer on same it used to work probably 90% of the time. In the new Betas it seems to work about 30% of the time. In fact I can take a file upload it, then do it again a second later and it will not skip it.

w/o posting session log and explaining in more detail there is no way to troubleshoot this.

In addition to the session log can you please specify which version of FlashFXP you're using?

If you're using build 1336 or up you may need to verify your file exist rules, we upgraded to a new rule system and your old rules were converted to the new system but its possible that they weren't converted properly. Or this might simply be a bug, Without the session log its hard to say.

So the rule is global (and for the site I am using for this example) for Downloading, Uploading, FXP'ing, same = Auto Skip. In this example its the same file a few seconds after each other.

I started notice this with the 3.7.8 betas

FlashFXP v3.7.8 build 1332 [BETA]
WinSock 2.0 -- OpenSSL 0.9.8i 15 Sep 2008

[L] 220---------- Welcome to Pure-FTPd [TLS] ----------
[L] 220-You are user number 1 of 50 allowed.
[L] 220-Local time is now 13:59. Server port: 21.
[L] 220-This is a private system - No anonymous login
[L] 220-IPv6 connections are also welcome on this server.
[L] 220 You will be disconnected after 15 minutes of inactivity.
[L] USER *****
[L] 331 User ***** OK. Password required
[L] PASS (hidden)
[L] 230-User **** has group access to:  ****
[L] 230 OK. Current restricted directory is /
[L] SYST
[L] 215 UNIX Type: L8
[L] FEAT
[L] 211-Extensions supported:
[L]  EPRT
[L]  IDLE
[L]  MDTM
[L]  SIZE
[L]  REST STREAM
[L]  MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
[L]  MLSD
[L]  ESTP
[L]  PASV
[L]  EPSV
[L]  SPSV
[L]  ESTA
[L]  AUTH TLS
[L]  PBSZ
[L]  PROT
[L] 211 End.
[L] CWD /www
[L] 250 OK. Current directory is /www
[L] PWD
[L] 257 "/www" is your current location
[L] TYPE A
[L] 200 TYPE is now ASCII
[L] PASV
[L] 227 Entering Passive Mode (96,30,3,44,117,108)
[L] Opening data connection IP: 96.30.3.44 PORT: 30060
[L] STOR ajax.php
[L] 150 Accepted data connection
[L] 226-File successfully transferred
[L] 226 0.093 seconds (measured here), 11.99 Kbytes per second
Transferred: ajax.php 1 KB in 0.08 seconds (15.0 KB/s)
[L] PASV
[L] 227 Entering Passive Mode (96,30,3,44,117,66)
[L] Opening data connection IP: 96.30.3.44 PORT: 30018
[L] MLSD
[L] 150 Accepted data connection
[L] 226-Options: -a -l 
[L] 226 26 matches total
[L] List Complete: 2 KB in 0.20 seconds (13.7 KB/s)
Transfer queue completed
Transferred 1 file totaling 1 KB in 0.70 seconds (15.0 KB/s)
[L] PASV
[L] 227 Entering Passive Mode (96,30,3,44,117,69)
[L] Opening data connection IP: 96.30.3.44 PORT: 30021
[L] STOR ajax.php
[L] 150 Accepted data connection
[L] 226-File successfully transferred
[L] 226 0.085 seconds (measured here), 13.17 Kbytes per second
Transferred: ajax.php 1 KB in 0.08 seconds (15.0 KB/s)
[L] PASV
[L] 227 Entering Passive Mode (96,30,3,44,117,48)
[L] Opening data connection IP: 96.30.3.44 PORT: 30000
[L] MLSD
[L] 150 Accepted data connection
[L] 226-Options: -a -l 
[L] 226 26 matches total
[L] List Complete: 2 KB in 0.52 seconds (5.4 KB/s)
Transfer queue completed
Transferred 1 file totaling 1 KB in 0.89 seconds (15.0 KB/s)

Are you a registered user? I don't see a license key attached to your account. There are currently 6 months of customers currently in limbo due to the server crash, so this may explain why I can't find your key. Or maybe you registered under another account?

Reason I ask is that as a registered user you can apply as a beta tester and gain access to beta releases before they're made available for everyone else.

The newer beta releases implement a new file exists rule system that is capable of comparing the size as well as date.

Based on your session log it looks like the php files are transferred in ASCII mode, in most cases the size will not be equal due to the conversion and thats most likely why the file doesn't get skipped.

Using the date comparison rule you could eliminate this limitation.

Yes I am a legit user. This should have been the account I signed up with, but I don't remember for sure. It was some time ago (6-29-2005). I can PM you with my info if you would like.

I would like to test that beta if possible. I do a lot of uploading over and over again and it would be nice to be able to skip files on a more regular basis.

Yes, Please PM me your info. The serial # in the about box should enough to validate your request.

Ok we got that worked out. Now I have build 1336 (maybe 1337??) and I still get the same result.

FlashFXP v3.7.8 build 1336 [BETA]
Support Forums at http://forum.flashfxp.com
Report a Bug at http://bugtracker.flashfxp.com
 
WinSock 2.0 -- OpenSSL 0.9.8i 15 Sep 2008
[L] 220---------- Welcome to Pure-FTPd [TLS] ----------
[L] 220-You are user number 1 of 50 allowed.
[L] 220-Local time is now 13:17. Server port: 21.
[L] 220-This is a private system - No anonymous login
[L] 220-IPv6 connections are also welcome on this server.
[L] 220 You will be disconnected after 15 minutes of inactivity.
[L] USER *******
[L] 331 User ***** OK. Password required
[L] PASS (hidden)
[L] 230-User ***** has group access to:  ****
[L] 230 OK. Current restricted directory is /
[L] SYST
[L] 215 UNIX Type: L8
[L] FEAT
[L] 211-Extensions supported:
[L]  EPRT
[L]  IDLE
[L]  MDTM
[L]  SIZE
[L]  REST STREAM
[L]  MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
[L]  MLSD
[L]  ESTP
[L]  PASV
[L]  EPSV
[L]  SPSV
[L]  ESTA
[L]  AUTH TLS
[L]  PBSZ
[L]  PROT
[L] 211 End.
[L] CWD /www
[L] 250 OK. Current directory is /www
[L] PWD
[L] 257 "/www" is your current location
[L] PASV
[L] 227 Entering Passive Mode (96,30,3,44,117,50)
[L] Opening data connection IP: 96.30.3.44 PORT: 30002
[L] MLSD
[L] 150 Accepted data connection
[L] 226-Options: -a -l 
[L] 226 27 matches total
[L] List Complete: 2 KB in 0.20 seconds (14.2 KB/s)
(debug) Rule #1 matched.
[L] PASV
[L] 227 Entering Passive Mode (96,30,3,44,117,111)
[L] Opening data connection IP: 96.30.3.44 PORT: 30063
[L] STOR ajax.php
[L] 150 Accepted data connection
[L] 226-File successfully transferred
[L] 226 0.090 seconds (measured here), 12.34 Kbytes per second
[L] MDTM 20090403210518 ajax.php
[L] 550 Can't check for file existence
[L] SITE UTIME ajax.php 20090403210518 20090403210518 20090403210518 UTC
[L] 250 UTIME OK
Transferred: ajax.php 1 KB in 0.08 seconds (15.0 KB/s)
[L] PASV
[L] 227 Entering Passive Mode (96,30,3,44,117,100)
[L] Opening data connection IP: 96.30.3.44 PORT: 30052
[L] MLSD
[L] 150 Accepted data connection
[L] 226-Options: -a -l 
[L] 226 27 matches total
[L] List Complete: 2 KB in 0.22 seconds (13.2 KB/s)
Transfer queue completed
Transferred 1 file totaling 1 KB in 0.75 seconds (15.0 KB/s)
(debug) Rule #1 matched.
[L] PASV
[L] 227 Entering Passive Mode (96,30,3,44,117,100)
[L] Opening data connection IP: 96.30.3.44 PORT: 30052
[L] STOR ajax.php
[L] 150 Accepted data connection
[L] 226-File successfully transferred
[L] 226 0.077 seconds (measured here), 14.48 Kbytes per second
[L] MDTM 20090403210518 ajax.php
[L] 550 Can't check for file existence
[L] SITE UTIME ajax.php 20090403210518 20090403210518 20090403210518 UTC
[L] 250 UTIME OK
Transferred: ajax.php 1 KB in 0.06 seconds (18.9 KB/s)
[L] PASV
[L] 227 Entering Passive Mode (96,30,3,44,117,83)
[L] Opening data connection IP: 96.30.3.44 PORT: 30035
[L] MLSD
[L] 150 Accepted data connection
[L] 226-Options: -a -l 
[L] 226 27 matches total
[L] List Complete: 2 KB in 0.20 seconds (14.2 KB/s)
Transfer queue completed
Transferred 1 file totaling 1 KB in 0.80 seconds (18.9 KB/s)

It says rule #1 was matched, what is the first rule defined as?

I see you changed the rules in this beta. Nice.
Rule #1 is if the destination is smaller than the transfer then overwrite. So it's still not seeing the file sizes correctly for some reason.

PS when the edit rule window open its not properly sized. Its height and width is a few pixels short so you get the scroll bars.

It would appear that the file transfer is being done in ASCII mode, in most cases when uploading to a unix style ftp server the file will be smaller due to the end of line conversion. Text files created on windows based machines are larger because they use two bytes for the end of line conversion where unix uses one byte.

If you have the option "only resume files transferred in binary mode" checked that may also be a factor.

Since the ftp server appears to support setting the file date/time on upload you might be better suited using the date compare instead of comparing by size.

I will disable the scrollbars on that dialog in the next build, please let me know if you continue to seem them in future releases.

No luck.

I unchecked the box for only resume in binary mode. I then changed the rule to skip if date and time with no luck. Then I switched all transfers to Binary (which I found another bug with) still nothing.

Here is what it says:

(debug) Rule #2 matched.
[L] PASV
[L] 227 Entering Passive Mode (96,30,3,44,117,56)
[L] Opening data connection IP: 96.30.3.44 PORT: 30008
[L] STOR ajax.php
[L] 150 Accepted data connection
[L] 226-File successfully transferred
[L] 226 0.079 seconds (measured here), 14.09 Kbytes per second
[L] MDTM 20090403210518 ajax.php
[L] 550 Can't check for file existence
[L] SITE UTIME ajax.php 20090403210518 20090403210518 20090403210518 UTC
[L] 250 UTIME OK
Transferred: ajax.php 1 KB in 0.08 seconds (15.0 KB/s)
[L] PASV
[L] 227 Entering Passive Mode (96,30,3,44,117,77)
[L] Opening data connection IP: 96.30.3.44 PORT: 30029
[L] MLSD
[L] 150 Accepted data connection
[L] 226-Options: -a -l 
[L] 226 27 matches total
[L] List Complete: 2 KB in 0.19 seconds (15.3 KB/s)
Transfer queue completed
Transferred 1 file totaling 1 KB in 0.73 seconds (15.0 KB/s)

Changing the transfer mode in the Preferences doesn't take effect until restart, you're changing the default transfer mode that is set on startup and not the current session transfer mode, this is changed via the Session menu > Transfer mode.

Ok so I changed the mode, closed and restarted it.

Now its prompting me on what to do and not following the rules when equal.

Are you still using compare by date as the rule? This FTP server doesn't support setting the file date on upload, so this will prevent compare by date from functioning in this situation on this specific FTP server.

Ok gotcha. So it works now just fine with transfer set to binary mode, the rule only checking for file size.