I’m curious what the methodology is behind the way that gmail (in their web client) offers a “view” and “download” links right next to each other for things like an attached .jpg file. I have found that the browser generally decides how it’s going to handle such things based on the file’s extension or mime type, but in this case, you have one file and two links and both behaviors offered to the user side by side.
I’m assuming it’s a server config thing, but I’d like to know what that is, exactly (or if I’m wrong, how they’re doing it on the client).
I’m curious what the methodology is behind the way that gmail (in their web
Share
It’s likely just setting a Content-disposition header at the server level for the “download” link (forcing a save as/open dialog), and allowing the browser to handle it normally for the view link.