Web Server Requirements for updates

Are there any specific web server requirements for wyBuild server files (wys) and wyBuild update files (wyu) to be accessed and downloaded by the wyUpdate.exe?

IIS 7? - MIME type registration? - Script handler? - Folder browsing permissions? - Anonymous access rights?

Apache? - .htaccess requirements? - Apache .config requirements?

The only requirement is that you get the files to the server. wyUpdate can download from http, https, or ftp links. Whichever is easiest for you.

The files are in the correct directory. I can also access other files (html) in the same directory correctly through the URL. However I get this error from wyUpdate.

"Error trying to save file "": Error downloading "http://localhost/Elements/POCC_Publish.wyserver.wys": The remote server returned an error: (404) Not Found.

If you use a web browser to access the URL it is a 404.3 Error indicating that the wys extension is not registered with script handling or as a MIME type. If it is meant to be downloaded and read by wyUpdate then I probably need to register the extension with IIS 7 as a MIME type so it can be downloaded. If it is meant to be rendered in the browser, then I'll have to know what type of script to process it as.

Here is the error when viewed through IE8

HTTP Error 404.3 - Not FoundThe page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.

I can register the MIME with IIS, but thought I'd check first to make sure I am not running down a rabbit hole. Have others had such issues on IIS7?

Ok, well if IIS requires you to register a mime type, then do something generic. Use "application/octet-stream" for the *.wyu and *.wys files.

Apache automatically handles all unregistered extensions as "application/octet-stream".

Also, by the way, we released 2.0.5 earlier this morning. It adds overriding server support to wyUpdate. All you have to do is specify the new site as an argument:

wyupdate.exe -server:"http://example.com/newserver.wys"

We'll add documentation to the wyBuild help site early next week.

Normally IIS does as well, I think this is a by product of having wyBuild installed on my box and having registered the extensions with the wyBuild program. This probably won't happen if wyBuild isn't installed on the same computer.

Also, by the way, we released 2.0.5 earlier this morning. It adds overriding server support to wyUpdate. All you have to do is specify the new site as an argument:

wyupdate.exe -server:"http://example.com/newserver.wys"

Rock! Thanks.

Just for confirmation, adding .wys and .wyu to the MIME type list in IIS7 corrected the issue. I set them both as "application/octet-stream". I was able to run an update via wyUpdate.

Hi,My update site and server site is not downloading my *.wyu files using wyupdates.exe. Is there any specific IIS/web server changes needs to be done to avoid this issue?

Because, direct URL is downloading the .wyu files but via Wyupdates.exe the download is not working and am getting the following error,

Error trying to save file: Could not download "https://website.aspx? update=file.wyu" - a web page was returned from the web server.

Also, want to add that, MIME type i have already set for .wyu and .wys files.

Please guide me is there any webfilter to be added or etc to access from wyupdates?

The fact that you have a space between the "file" and the parameters is probably causing the problem:

https://website.aspx? update=file.wyu

Instead of this

https://website.aspx?update=file.wyu

But much more information is needed (log files, legwork on your end, like copy&pasting the URL in a web browser to see what your server is returning, etc.).