diff options
| -rw-r--r-- | posts/2021-10-22-forced-downloads-in-the-browser-via-http.php | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/posts/2021-10-22-forced-downloads-in-the-browser-via-http.php b/posts/2021-10-22-forced-downloads-in-the-browser-via-http.php index 958a2b1..bd411e5 100644 --- a/posts/2021-10-22-forced-downloads-in-the-browser-via-http.php +++ b/posts/2021-10-22-forced-downloads-in-the-browser-via-http.php @@ -11,7 +11,7 @@ include($_SERVER['DOCUMENT_ROOT'] . '/includes/head.php'); </p> <p> - Let's say you want to genreate a file server-side and send it back to the client's browser to download. If it's plain text, the browser will usually try to render it in a tab, without prompting the user what they want to do with it. The user could then save the page with <code>^s</code> but that's less than ideal. Ideally, they would click a link/submit a form, and immediately be prompted to save the file to save the file to disk and even open it in a local application. If they elect to always perform that action with files of that kind, the download will start immediately. + Let's say you want to generate a file server-side and send it back to the client's browser to download. If it's plain text, the browser will usually try to render it in a tab, without prompting the user what they want to do with it. The user could then save the page with <code>^s</code> but that's less than ideal. Ideally, they would click a link/submit a form, and immediately be prompted to save the file to disk and even open it in a local application. If they elect to always perform that action with files of that kind, the download will start immediately. </p> <h2>The Default: Rendering in a Tab</h2> |