Forums

Hi guys,

I've got a small question that I wanted to ask you guys. In my workplace, we recently got a new and powerful server in which we have successfully transferred some of our databases to (from the old server to the new one). A problem that I have recently come across, is that a piece of coding that usually allows our clients to download certain files via a Web Browser (usually I.E.) has stopped working now that the database has been shifted to the new server. On the old server, the coding worked fine and displayed a dialogue box allowing the user to download the chosen file, however, the coding doesn't seem to work now. I did have a couple of assumptions; that it could be either that the I.E. is a different version hence, the coding doesn't work as normal, that there is a fault with the communication between the new server and our main server (which is where the files are downloaded from) or that there is some sort of file that is missing.

Does anyone have an opinion on this? I would be most grateful for your time and opinion.

Omash

I'm assuming that you're sending the browser a URL that equates to the file, in which case the move to another box is more likely something in your IIS setup or similar rather than a Jade issue. I'd start by taking Jade out of the mix and just construct the appropriate URL in your browser and then tweak any relevant IIS settings until such time as you get the downloads working. Once you can hit the URL directly and have the download work then you can try using your Jade application again, but until you can get it working independent of Jade there's not much more that can be suggested on these forums. It may be more relevant to try looking for an IIS forum if you can't get it working with Jade taken out of the mix.

Cheers,
BeeJay.

Omash,

If you are using the JadeHTMLClass::replyAsBinary method to send the downloadable "file" to the client browser, then you may have the same issue as described in another post:

https://forums.jadeworld.com/viewtopic. ... =iis#p6669

This issue relates to some changes in the way IIS deals with this type of reply in IIS 7 and 7.5.

Regards,
Kevin Douglas

Hi BeeJay and kpd,

I just wanted to thank you guys as both of you are correct and by following kpd's link, the problem has been solved. Thank you for your time and help!

Omash