I think from prior debugging questions it's a text file on the server.stan_qaz wrote:Isn't the update file on the server HTML? If it is could you set a short expire time on it to keep it from being cached for long?
http://www.web-caching.com/mnot_tutorial/how.html
Can't update Version 2010 1.0.15
-
Sidewinder
- Weary Womble
Post
Re: Can't update Version 2010 1.0.15
I am not a Firetrust employee. Just a MW User & Volunteer BETA Tester.
Remember "FREEDOM IS NEVER FREE" U.S.N.
DT W7 64 HP SP1 16GB Ram - LT W7 32 HP SP1 4GB Ram - iPad4 64 GB Ram WiFi/Cellular IOS 9.3 Beta 3
Remember "FREEDOM IS NEVER FREE" U.S.N.
DT W7 64 HP SP1 16GB Ram - LT W7 32 HP SP1 4GB Ram - iPad4 64 GB Ram WiFi/Cellular IOS 9.3 Beta 3
- johnfairweather
- Travelling Tuatara
Post
Re: Can't update Version 2010 1.0.15
This was an icon, which was in my Start Menu (on my Netbook), clicking on it showed that Version 1.0.19 was available. I then clicked on 'Update' on both my Netbook and PC, but Mailwasher told me that the software was up to date. Clicking on this icon then took me to the Mailwasher website update page, where I downloaded version 1.0.19 to my Netbook. For my PC, I couldn't see this icon, but that is my PC's problem.
==================================================================================================================================
==================================================================================================================================
rusticdog wrote:Can you clarify this last statement, which Windows Updater told you there was a MailWasher update ?johnfairweather wrote:Likewise, clicking on 'Update', I get a message saying that my software is up-to-date. I only found that there was an update, by clicking on my 'Windows Updater', just by chance.
We are really starting to draw blanks on why the update process is being so unreliable for some folk. We think we have all the kinks worked out, but it just seems to tell some folk they are up to date. I was thinking that possibly some ISPs that do heavy caching might be caching the file that is streamed in, so MailWasher isn't actually checking the file against the live copy on the server, but a locally cached copy through the ISP that's not yet up to date.