Skip to main content

Download File Using jQuery



How can I prompt a download for a user when they click a link.





For example, instead of:







<a href="uploads/file.doc">Download Here</a>







I could use:







<a href="#">Download Here</a>



$('a').click... //Some jquery to download the file







This way, Google does not index my HREF's and private files.





Can this be done with jQuery, if so, how? Or should this be done with PHP or something instead?





Thanks!



Source: Tips4all

Comments

  1. I might suggest this, as a more gracefully degrading solution, using preventDefault:

    $('a').click(function(e) {
    e.preventDefault(); //stop the browser from following
    window.location.href = 'uploads/file.doc';
    });

    <a href="no-script.html">Download now!</a>


    Even if there's no Javascript, at least this way the user will get some feedback.

    ReplyDelete
  2. If you don't want search engines to index certain files, you can use robots.txt to tell web spiders not to access certain parts of your website.

    If you rely only on javascript, then some users who browse without it won't be able to click your links.

    ReplyDelete
  3. Here's a nice article that shows many ways of hiding files from search engines:


    http://www.antezeta.com/blog/avoid-search-engine-indexing


    JavaScript isn't a good way not to index a page; it won't prevent users from linking directly to your files (and thus revealing it to crawlers), and as Rob mentioned, wouldn't work for all users.
    An easy fix is to add the rel="nofollow" attribute, though again, it's not complete without robots.txt.

    <a href="uploads/file.doc" rel="nofollow">Download Here</a>

    ReplyDelete
  4. Yes, you would have to change the window.location.href to the url of the file you would want to download.

    window.location.href = 'http://www.com/path/to/file';

    ReplyDelete
  5. See here for a similar post on using jQuery to clear forms: Blank out a form with jQuery

    You may also be running into an issue where the values are being repopulated by the struts value stack. In other words, you submit your form, do whatever in the action class, but do not clear the related field values in the action class. In this scenario the form would appear to maintain the values you previously submitted. If you are persisting these in some way, just null each field value in your action class after persisting and prior to returning SUCCESS.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex