Sending the javascript redirection to the callback client is actually the second call to the generator page. Note: this will cause the onload event to be triggered in IE because it works like a regular page. Remove content from the cache and send it to the client.
This is the code behind it, and this is what you really need. QueryString[ "data" ]! Write "Javascript to tell user there was a problem. AppendHeader "Pragma", "no-cache" ; Response. AppendHeader "content-size", data. ToString ; Response. I am loading a file just for an example using System. Open using System. Length ]; reader. Read data, 0, data. Insert reportKey, data, null, DateTime. Chrome and other such browsers auto-download the files where this condition will fail.
Lucky that is only by default. It is entirely possible a user of Chrome will specify where downloads should be saved and hence see the dialog box — ESR. Add a comment.
Don't eval code inside setTimeout 'getstatus ', ;. Use the fn directly: setTimeout getstatus, ; — Roko C. Jerzy Gebler Jerzy Gebler 9 9 silver badges 13 13 bronze badges. What if the user clicks the window? The hide is not getting called in my case — Prashant Pimpale. Worked for me for a pdf download with only some line of codes — Chris. My case is working on JSP and click to download csv. It works. Show 1 more comment. There are four known approaches to dealing with detecting when a browser download starts: Call fetch , retrieve the entire response, attach an a tag with a download attribute, and trigger a click event.
Modern web browsers will then offer the user the option to save the already retrieved file. There are several downsides with this approach: The entire data blob is stored in RAM, so if the file is large, it will consume that much RAM.
For small files, this probably isn't a deal breaker. The user has to wait for the entire file to download before they can save it. They also can't leave the page until it completes. The built-in web browser file downloader is not used. A cross-domain fetch will probably fail unless CORS headers are set. The iframe fires a load event if a page loads in the iframe instead of starting a download but it does not fire any events if the download starts.
Setting a cookie with the web server can then be detected by Javascript in a loop. There are several downsides with this approach: The server and client have to work in concert. The server has to set a cookie. The client has to detect the cookie.
Cross-domain requests won't be able to set the cookie. There are limits to how many cookies can be set per domain. Can't send custom HTTP headers. Use an iframe with URL redirection. The iframe starts a request and once the server has prepared the file, it dumps a HTML document that performs a meta refresh to a new URL, which triggers the download 1 second later.
The load event on the iframe happens when the HTML document loads. There are several downsides with this approach: The server has to maintain storage for the content being downloaded. Requires a cron job or similar to regularly clean up the directory. The server has to dump out special HTML content when the file is ready.
The client has to guess as to when the iframe has actually made the second request to the server and when the download has actually started before removing the iframe from the DOM. This could be overcome by just leaving the iframe in the DOM. The iframe triggers the download request. As soon as the request is made via the iframe, an identical request via XHR is made.
If the load event on the iframe fires, an error has occurred, abort the XHR request, and remove the iframe. If a XHR progress event fires, then downloading has probably started in the iframe, abort the XHR request, wait a few seconds, and then remove the iframe. This allows for larger files to be downloaded without relying on a server-side cookie. There are several downsides with this approach: There are two separate requests made for the same information.
The server can distinguish the XHR from the iframe by checking the incoming headers. If the server waits to send headers until the file data is ready, the XHR can roughly detect when the iframe has started to download even without CORS. The client has to guess as to when the download has actually started to remove the iframe from the DOM.
Can't send custom headers on the iframe. CubicleSoft CubicleSoft 1, 15 15 silver badges 18 18 bronze badges. Elmer Elmer 8, 1 1 gold badge 44 44 silver badges 35 35 bronze badges. Still has the issue of switching window and returning which will cause the modal to hide.
JQuery is supported but not required. Community Bot 1 1 1 silver badge. Jorge Paulo Jorge Paulo 3 3 silver badges 4 4 bronze badges. Art Geigel Art Geigel 1, 3 3 gold badges 19 19 silver badges 23 23 bronze badges. MB33 MB33 71 1 1 silver badge 1 1 bronze badge. It's works perfectly. Thanks for this beatiful sample. I'm very late to the party but I'll put this up here if anyone else would like to know my solution: I had a real struggle with this exact problem but I found a viable solution using iframes I know, I know.
It's terrible but it works for a simple problem that I had I had an html page that launched a separate php script that generated the file and then downloaded it. Walker Boh Walker Boh 6 6 silver badges 13 13 bronze badges. If the file is ready, do the download.
If the file is not ready, show the progress. New configurations have been added with Antidetect Browser 9, you can access the configurations for free on our site and you can share your own configurations. You can download newest version of Antidetect browser its completely free antidetect coded for the end user and free of charge. Do not rely on people and sites that tell you can buy the antidetect browser or antidetect crack for a fee as we clarifed before antidetect browser is completely free.
If not, could you do something like this: Generate a unique URL to download a given file. Only allow downloads from that user and during the window. The window should be long enough for the user to notice the transfer failed and to re-try once or twice, but no longer. The end result is: You can be reasonably sure the file is only being downloaded by the intended recipient. You can be sure that recipient can only download the file during a short window.
The same user could download the file more than once, but who cares? It's no different than making a local copy of the first file. It's an external contractual requirement: A given user may download the file once. The problem is determining when that event has happened.
You're right, of course, about the ease of copying once a file is downloaded. You can't apply logic too stringently here, it's not purely a technical issue.
David: bummer. In the absence of any built-in feature which I don't think exists you are relying on the client to tell you when the download is finished, and that's inherently unreliable; it wouldn't be too hard for a client to set up a proxy that blocks that confirmation from being sent out. Have you thought about setting up a packet sniffer or network monitoring tool that can tell you if all of the file's packets have been sent out?
Still doesn't mean they were successfully received , but its more reliable than "hey browser, let me know when you're done" : — Seth Petry-Johnson.
If it were possible, given the low sophistication level of our users and the ability to time-limit the damage that could be done by a more-sophisticated attacker, it would likely be reliable "enough" to satisfy the contractual requirement i. But based on the replies so far, I'm confirming my suspicion that it isn't possible. Thanks for taking the time! Sign up or log in Sign up using Google. Sign up using Facebook.
Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog.
0コメント