Bear Bibeault wrote:P.S. Who on earth is still using IE?
Who indeed. I thought it had been "edged" out.
Next up: fart jokes. I'm just full of mature humor today.
Seriously, the "Save As" menu item on a web browser simply stores a copy of the displayed web page - usually in its original HTML and often with a sub-directory containing the page dependencies (CSS, JavaScript, images and so forth). More often what you'd really like is some sort of text document such a a
Word document, Excel spreadsheet, PDF or the like. Save As cannot do that (except maybe a really crude form of PDF if you have suitable print options).
The common solution is that you'd have a "Save" or "Download" (or "Print") button on the web page that was connected to a URL which would return the document in its desired format and having a Content-Disposition header to suggest that the webapp client would want to save it on their local machine. When the client receives a response containing such a header, it can then pop up a "File Save" dialog box.
Under no circumstances is a web page supposed to be able to write out files (or print documents or do many other things) without first obtaining permission from the web client's user (dialog). That's how you get viruses. And server applications can't write directly to client filesystems either. Webapp servers aren't file servers and HTTP doesn't support access to the client's file system.