Time zone determination bugs

Logging into a site in the US from Britain, I noticed that the beta shows this:

[15:01:41] MDTM .htaccess
[15:01:41] 213 20080322230413
[15:01:41] Timezone offsets: Server: -25213 seconds. Local: -3600 seconds. Difference: 21613 seconds.

Britain is in BST right now -- GMT+1. The time zone offset should read +3600 not -3600. The server is in PDT, so the server offset (-7 hours) is nevertheless correct.

The file in question reports, to LIST, a date of 2008-03-22 22:04.

(I'm baffled as to how you're reading the server's time zone though.)

OK, another US server:

File: 2008-08-04 20:55
FlashFXP:
[15:18:02] MDTM .htaccess
[15:18:02] 213 20080804215506
[15:18:02] Timezone offsets: Server: -6 seconds. Local: -3600 seconds. Difference: -3594 seconds.

I forget where that server is, but nowhere in the USA is less than GMT-5.

Tried it on my domain's server, in Boston -- MDTM is supported (reported by FEAT) but no attempt to calculate time zones is made. Might be a left-over setting from when they upgraded ProFTPd (and refused to admit it) and the site was broken with FlashFXP 2; I turned off resume checking because it was leaving the server in a wrong state.

I do have three UK servers I can try, but none support FEAT :P

for the server time it takes the time from a file in the listing (the file must have a complete date, normally that requires a file created within the last 12 months) and then issues MDTM and calculates the difference to determine how much from GMT the listing date is.

We then get your local time and calculate the difference between GMT and we're able to determine the difference between local and remote.

I'm not sure why your local time isn't correct, you need to make sure its properly configured within windows.

I've done some tests though while limited they are always correct.

My PC's time zone is "(GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London", and "Automatically adjust clock for daylight saving changes" is ticked.

I'm in Windows 2000, if that makes a difference. However, -3600 instead of +3600 is a difference of two hours, which I really can't account for. If it was only a DST-related mistake, that would only put me out by one hour, not two.

Very odd. As I recall though, the API call needed to fetch this information is pretty horrendous and, while I've used it, I was never sure whether I was doing it right or not, and didn't really have anyone to ask.

I discovered a calculation issue when handling -/+ GMT, everything was treated as - GMT and thats why for your timezone it was wrong.

I had to set my local computer timezone to a + GMT timezone to notice the mistake.

Here's a fixed build for you to test
http://download.flashfxp.com/beta/ffxp3.7.3.1276.zip

OK, my time zone now shows up as 3600. Offset to the server I normally use, 8.00361..1 hours, not bad considering how flaky my PC's clock is.

That part is working from my end now. Thanks.

(Not counting what appears to be all the servers that lie about their time zone.)

Don't know if this is the same problem i had but i had a 2h offset in the 2 latest versions of betas. Downgrading to the version posted in this thread fixed it (3.7.3.1276)

no this is unrelated.