Weird SSH upload problem with WinSCP v.3.8.x

Hello.

I have a weird SSH upload problem with WinSCP v.3.8.x:

I've been using WinSCP for some time now and have never experienced the following before...

I'm trying to upload a file extension, '.tpl' which is a Smarty template extension. I transferred this file like any other file and everything looks fine - even when I review the contents of the transferred file on the remote (right side of window that represents the web server), I see the changes I've made to the file before uploading...SAME TIMESTAMP and EVERYTHING. So far, so good.

I pull up the webpage (IE v.6) and guess what...no change! I refresh the cache (ctrl-F5) of my browser AND have closed all browsers and even looked at it in FireFox...and guess what?...no change. I've check the webpage on a different computer and...no change. I upload the file again using ws_FTP and voila...change! It's like the file is going to the remote side of WinSCP but the server only checks to see if the file name is there but doesn't read the new changes. The reason I know it recognizes the file is because I renamed the file so the web server couldn't find it and a [file missing] error was received. I changed the file name back and the old content from the previous (not current) change was still showing up via the browser. I then made another change to the file (so now it's 2 generations of changes to the file) and the ORIGINAL change is still there, not the 1st nor 2nd revision of the file. ws_FTP (really old version) uploads the file with no problem.

Does anyone know how come this is? I've tried both ascii and binary with...no change. It's like the code is in a mirror, but untouchable for executing. There seems to be some kind of 'cache' that is not letting go to allow the '.tpl' file to be recognized. I upgraded from v.3.8.1 to 3.8.2 yesterday and problem still exists. I had not changed any software params or configuration. Problem came out of the blue...

Thanks in advance.

P.S. I looked in this forum to see if anyone else experienced this and I think I saw 2 (didn't bookmark - used 'cache' as search word)

Does the WinSCP set the timestamp of uploaded file in a different way than WS_FTP does?

Thanks for your reply.

As a matter of fact, yes...

WinSCP 11:51:14
ws_FTP 02:51

Thanks.

Hello again.

Last post continued...

UPDATE (new finding)
--------------------
I just noticed something:

When I upload via WinSCP, the remote side shows that the upload was successful with the correct timestamp. When I reload the webpage, the previous version is still current - the uploaded version did not actually take effect. It's like it's uploading to some temporary location, not to the actual server account folder location.

When I view the remote side in Tunnelier, it shows the timestamp of the PREVIOUS version - it matches what is actually viewed on the web (the upload went to the correct folder on the webserver).

When I then upload via Tunnelier, the timestamp changes to the same timestamp of the 'current' version and the webserver is subsequently updated and shows the 'right' version.

HTH.

Thanks.

EDIT: btw - the timestamp in WinSCP after upload via Tunnelier is subsequently changed e.g. timestamp on PC is 1:25 PM, timestamp after upload via WinSCP is 1:25 PM (but the webserver is not actually updated - still displaying previous file version); timestamp in Tunnelier after uploaded via Tunnelier is 1:25 PM. Going back to WinSCP, the timestamp has changed to 2:25 PM with the webserver serving the most current verion of the file.

EDIT#2: btw - I want to resolve this because I really like WinSCP and actually prefer its usability.

you have a php cacher that is caching the previous page. The remote file changes at the os level but the web output doesn't. . . right? that would be a cache of some sort. if you're working with an os guru, ask em if they have 'eaccellerator' or other php (or even html) caching system.

Thanks for your reply.

This is somewhat outside of my realm but...

What is it about WinSCP that would make it more affected by this than say, Tunnelier or ws_FTP?

Is there a setting within the software to disable this type of caching?

Thanks.

uploader wrote:

What is it about WinSCP that would make it more affected by this than say, Tunnelier or ws_FTP?

It can be the way it sets the timestamp of remote file. Something that prevents the cache recognising the new version.