Downloading - timestamp

allawrence · Post by **allawrence** » Sat Aug 14, 2004 3:18 am

When I download a file it does not maintain the same date and time as the original file.. here is an example...

The orginal file has a file date/time of: 08/13/04 21:41

After downloading it the file, on my
system, has a date/time of: 08:14:04 02:41

All I want is for the downloaded file to maintain the SAME date/time as the orginal file on the remote site.

What could I be doing wrong? Settings incorrect?

Thanks in advance!

Al

allawrence · Post by **allawrence** » Sat Aug 14, 2004 11:18 am

CP wrote:I think there is a response here (click on this link and scroll down).

http://www.coreftp.com/forums/viewtopic.php?t=219

If that didn't help, there is another option you can try if your server does not support MDTM, go to the advanced - transfer settings of a site profile and turn off the MDTM settings (check 'do not use mdtm for date time' black). If you don't use MDTM it should use the remote time date stamp that you see.

Now when I download the file/date on my system reflects the CURRENT date/time and not the remotes date/time

This happens regardless of the MDTM setting...

Did not do the +/- setting as it does not appear to be relevant for this issue

allawrence · Post by **allawrence** » Sat Aug 14, 2004 8:48 pm

CP wrote:If the MDTM command is supported, the dates should match. In your log, do you see the 'MDTM filname' command being displayed after download?

If MDTM is not used, it will default to the time date stamp found in the remote directory listing (right click on the remote directory, select directory commands, directory info).

Do NOT use MDTM is checked.... and it is NOT defualting to the date time in the remote directory..
Here is a snippit of the log:

00 Type set to A.
PASV
227 Entering Passive Mode (64,49,236,50,9,15)
RETR dfjim.bat
Connect socket #700 to 64.49.236.50, port 2319...
150 Opening ASCII mode data connection for dfjim.bat (57 Bytes).
226 Transfer complete.

If want me to try somehting else please let me know...

allawrence · Post by **allawrence** » Sun Aug 15, 2004 2:17 am

CP wrote:There was a problem (guess there's been too much testing with servers that support MDTM). The update will be in build 1362.

The 'developer build' (check the download section) will have the update shortly.

Download and installed 1362 but it still exhibits the same problem... NO MDTM does not pick up the remote date/time rather it uses the current date/time...

Al

allawrence · Post by **allawrence** » Sun Aug 15, 2004 2:23 am

allawrence wrote:
CP wrote:There was a problem (guess there's been too much testing with servers that support MDTM). The update will be in build 1362.

The 'developer build' (check the download section) will have the update shortly.
Download and installed 1362 but it still exhibits the same problem... NO MDTM does not pick up the remote date/time rather it uses the current date/time...

UPDATE:

If I UNCHECK the "Do not use MDTM...." it picks up the REMOTE date/time...

allawrence · Post by **allawrence** » Sun Aug 15, 2004 2:31 am

allawrence wrote:
allawrence wrote:
CP wrote:There was a problem (guess there's been too much testing with servers that support MDTM). The update will be in build 1362.

The 'developer build' (check the download section) will have the update shortly.
Download and installed 1362 but it still exhibits the same problem... NO MDTM does not pick up the remote date/time rather it uses the current date/time...
UPDATE:

If I UNCHECK the "Do not use MDTM...." it picks up the REMOTE date/time...

Did some more testing and this gets more bizzarre...

I tried a much larger file (if that matters) and this file date/time is assigned a time that is 5 hours ahead of the REMOTE. Why would it do that with one file and not with the other 2 I downloaded. The 2 files that had the correct date/time were very small and OLD files dated 2002 and the new larger file had today's date and a time of 2 hours ago (ont the REMOTE side)...

allawrence · Post by **allawrence** » Sun Aug 15, 2004 10:17 am

CP wrote: Updated it again, give build 1363 a try...

Should have tested that change a little more before rushing it out the door like that.

Chris

Happens to the best of us form time to time.... <g>

Just tried to download via FTP and HTTP and the downloads still say 1362

allawrence · Post by **allawrence** » Sun Aug 15, 2004 7:47 pm

CP wrote:I just installed all four links, all are build 1363. Maybe what was installed was a version cached in your browser? Or if you had Core FTP running when you installed, the latest version won't install over it until you reboot...

Hmmmm, I would assume I had Core FTP running, but I know I brought it down and back up after each upgrade attempt...

Is there not some way to notify us the process is running and give us an opportunity to stop the process OR terminate the running process programatically, before attempting to update?

Do I need to actually REBOOT or just not have Core FTP running when I update?

allawrence · Post by **allawrence** » Sun Aug 15, 2004 8:06 pm

CP wrote:Right, just do *not* have Core FTP running when you install. This will most likely be fixed in the 2.0 install version in the near future.

Great! The less I have to worry about when it comes to installing,etc the better... SEAMLESS is my motto <g>....

Be back to you as soon as I can upgrade again....

allawrence · Post by **allawrence** » Sun Aug 15, 2004 8:15 pm

CP wrote:Right, just do *not* have Core FTP running when you install. This will most likely be fixed in the 2.0 install version in the near future.

OK, here is what I have found...

(1) Downloaded using FTP and it did NOT give me the 1363 version...

(2) Downloaded using HTTP and it DID work

(3) Tested the fix and it did not fix it... the date/time of a download still uses the CURRENT date/time rather than the date/time of the remote file

allawrence · Post by **allawrence** » Mon Aug 16, 2004 10:19 am

CP wrote:I updated the server again with build 1363... Downloaded and tested all 4 downloads. Works ok here... Hope it works this time!?

(1) Downloaded and instyalled using FTP and the version is 1362

(2) Downloaded and installed using HTTP and the version is 1363

(3) The 1363 version download using HTTP does NOT fix the problem. Downloaded file still displays the CURRENT date/time on my system.

Perhaps an uninstall and reinstall is in order???
Is there a way to revert all settings back to original settigns at install without a reinstall?

Just grasping at straws here...

allawrence · Post by **allawrence** » Mon Aug 16, 2004 3:18 pm

CP wrote:You can un-install but that shouldn't be necessary.

Let's double check your settings.

Go into the site manager, click your site, click advanced, transfers, and make sure 'do not use mdtm' is checked (black, not gray).

Connect to your ftp server.

Download a file.

The times should now match.

I'll try testing on a few other machines in the meantime!

'Do not use mdtm' IS checked and it is BLACK on WHITE

Downloaded a file and they do not match...

If you want me to try anything else let me know... would be more than happy to...

allawrence · Post by **allawrence** » Mon Aug 16, 2004 3:25 pm

allawrence wrote:
CP wrote:You can un-install but that shouldn't be necessary.

Let's double check your settings.

Go into the site manager, click your site, click advanced, transfers, and make sure 'do not use mdtm' is checked (black, not gray).

Connect to your ftp server.

Download a file.

The times should now match.

I'll try testing on a few other machines in the meantime!
I tried another site and downloaded a few files and that did not alter the outcome... still uses current date/time

'Do not use mdtm' IS checked and it is BLACK on WHITE

Downloaded a file and they do not match...

If you want me to try anything else let me know... would be more than happy to...