It would be nice to have the user get a different page (to upload another file? with a processing results summary?) after they click "process", instead of just getting the download directed at them. This is a little tricky, since you can't use Content-Disposition: Attachment (which initiates the download) and have normal rendered HTML page content in the same HTTP response. So we'd need to track the processing session/results across the interstitial and use e.g. <meta refresh> to an endpoint with Content-Disposition: Attachment to start the download.
It would be nice to have the user get a different page (to upload another file? with a processing results summary?) after they click "process", instead of just getting the download directed at them. This is a little tricky, since you can't use
Content-Disposition: Attachment(which initiates the download) and have normal rendered HTML page content in the same HTTP response. So we'd need to track the processing session/results across the interstitial and use e.g.<meta refresh>to an endpoint withContent-Disposition: Attachmentto start the download.