I am not sure if I am missing some form of setting, but when trying to set up an auto-update process to download support files it seems to work for some file types, but not for others. This is an update through http.
We have a custom binary support file I wish to make available for update. The file extension is not that important right now, but I was trying with *.ersf or *.rsf. After a few hours of head scratching (TWebUpdate stuff usually just seems to work, though most of what we have done has been through ftp) I finally decided to try simply renaming the file to *.txt (even though it isn't), and the download then works like a charm.
So it would appear that there is some form of file filtering based on the extension. I am trying to work out whether this is a Microsoft thing, and http thing, or a TWebUpdate thing. I really would like to stick with the http route, as ftp is hard to get our company to allow.
I also really would prefer not to have to go the route of false naming files and renaming later, as it removes some of the elegance of doing most of this through the TWebUpdate *.inf file.
Any help gratefully accepted.