I’d just add that the file-extension is not the only means to specify handling. The webserver also has the opportunity to specify a MIME type for the resource. But either way, if the browser’s conclusion about the filetype is that it’s a known one it will try to display it or launch a plugin
To request that a browser treat a requested resource as something that must be saved and not displayed, try using http-equiv or other means to send this header (where fname.ext is the filename you would like the browser to default to).
Content-disposition: attachment; filename=fname.ext
#webMethods-Architecture#Integration-Server-and-ESB#webMethods-General#webMethods