Even that stuff won't really help a lot.
Even if you can make a browser turn off view source, I can wander up to your webserver with a telnet session and GET the source. I can cut the Javascript out and run it through an interpreter and then, having got the URL, I can send HTTP GETs to get the resource.
You /cannot/ in any way trust client side code to do your security for you.
If your thing is that you want people to ONLY be able to look at the resource in a browser, and not save off a copy, you're probably onto a loser; any access method a browser uses, someone can spoof. At the limit, even naive users could just copy the resource out of their browsers cache directory
If it's that you just want your AUTHORISED users to be able to download the resource, you have two issues; one is that once downloaded they can copy it. That can be solved, but only by using DRM systems which will limit your audience.
The second is preventing people from just emailing out the URL. This is doable by sending out tags to the customers. The server side script checks the tags haven't been used before. So even if someone sends it to their friend, they can't re-use the url.
{Solving the aggro of a user who initiates download, but his session breaks is an exercise for the reader. Probably involves allowing a restarted HTTP download to work from some offset into the file if the ident has been used before. Icky.}