How to prevent direct file access in your wp-content directory

- by

I was working on a secure site with sensitive video material that we needed strict members access to. Even though many plugins can make sure your direct permalinks can only be seen by logged in members, direct links to files in your wp-content directory are still accessible to others. They can even be hotlinked from other sites.

One way around this is to move the wp-content directory outside the web visible portion of your directory on the server, but even so WordPress can always link to such files. A better way is to tell your server not to give access to certain files (say ending with mp4 or mp3) and only allow access from your own domain.

We can use Apache Mod Rewrite for this – it’s a complex language that you can utilise in your .htaccess file within the wp-content folder.

Let me show you how to keep prying eyes out of your content.

The Problem

Say you had a PDF file that you’d like visitors on your own site to download.

However, if someone were to copy this link and call it from a browser window directly, or if they were to post the link to you PDF on another website then the document shall not be accessible. By default it is. Let’ fix that.

The Solution

Upload a .htaccess file into your wp-content folder. Have a look if one exists already, then append this code to the end of the file. If you don’t have one, just create a new blank file and add this code to it:

RewriteEngine On
RewriteCond %{HTTP_REFERER} !^http://(www\.)?yourwebsite\.com/ [NC]
RewriteCond %{REQUEST_URI} !hotlink\.(gif|png|jpg|doc|xls|pdf|html|htm|xlsx|docx|mp4|mov) [NC]
RewriteCond %{HTTP_COOKIE} !^.*wordpress_logged_in.*$ [NC]
RewriteRule .*\.(gif|png|jpg|doc|xls|pdf|html|htm|xlsx|docx|mp4|mov)$ http://yourwebsite.com/ [NC]

This rather strange sounding code is neither Linux nor PHP nor MySQL – it’s Apache (that’s the service which usually takes care of serving up those websites from a server). These are instructions that will tell Apache to do the following – I’ll explain this line by line:

  • here are some instructions I’d like you to use in this directory
  • IF someone comes from anywhere other than yourwebsite.com
  • AND they ask for a direct file that ends with any of the following (gif, png, jpg, etc)
  • AND they are not logged into WordPress on this domain
  • THEN direct every link to such files to http://yourwebsite.com

If these conditions are not met, then give out the file – everyone’s happy.

Why do I need this?

To prevent people hotlinking to your files. One aspect is security: say you have sensitive material that you only want your direct visitors to see. Or imagine you had a members area and give out a PDF that you’d like only logged in visitors to see without an encrypted link.

The same goes for image files or videos hosted on your site which you’d like to embed into your own pages but not allow embedding on external sites.

I had a guy once hotlink one of my images as his MySpace profile, the background graphic came from my server. If you’re on a plan with bandwidth limitations this can get you into trouble.

What else do I need?

Make sure you have an Apache web server running on your website, and that user overrides (i.e. .htaccess directives) are allowed.

When I wrote this article in 2012 this was a given, but since then the internet landscape has changed slightly. Nowadays, other web servers such as NGINX are commonplace, with which the above code will not work. Your web hosting company will be able to tell you more about your hosting environment.

Usage Examples

You can use this solution to conserve load and bandwidth on your server. For example, other users won’t be able to embed images hosted on your server in their websites (unless they upload them to their own), and sensitive files can only be shared on your own website.

However, this does not mean that sensitive files cannot be accessed at all; they are still available for download if visitors come via your website. Here’s an example of how to this solution works

  • you have a sensitive file at http://you.com/file.pdf
  • users coming from http://anywhere.com and click on that link will be redirected to your home page
  • users currently surfing http://whatever.com can paste your link into their browser bar will be redirected to your home page
  • users currently surfing your own website http://you.com can paste the link into their browser bar and will also be redirected to your home page, unless they are logged in to WordPress
  • if users are logged in to WordPress, and are currently surfing your website, and would paste the link to the file into their browser bar, they will get access

Alternatives

I’ve received many comments on this article over the years, with many suggested use cases and questions. It’s important to understand that while the above solution is a quick fix for preventing direct access sensitive files in certain cases, it is NOT a replacement for a full membership website.

If you’re selling anything downloadable and would like to make sure only authorised users have access to the files you provide, I suggest a membership plugin like WP eMember by Tips and Tricks HQ.

Further Reading

These articles discuss the same subject:



If you enjoy my content, please consider supporting me on Ko-fi. In return you can browse this whole site without any pesky ads! More details here.

117 thoughts on “How to prevent direct file access in your wp-content directory”

  1. This didn’t work for me. Uploaded the .htaccess to the wp-content folder then went to my website, logged out then entered a url direct to a pdf file in the browser and it opened just fine. Is there some caching going on or is it possible my web server is not using Apache?

  2. Hi Andy, both of these scenarios are indeed possible. Let’s check one after the other.

    I’d test setups like this with two different web browsers, one in which you’re logged in, and another one in which you’re not (say Chrome and Firefox). Therefore you can make a change and see how the non-logged in browser is affected by it. Using the same browser may indeed give you caching issues and false results.

    To test if your server is running Apache or NGINX, open Terminal or a Command line tool of your choice, then type

    telnet yourdomain.com 80

    Replace yourdomain.com with your actual domain or your server’s IP address. Now we’ll make a simple http request and read the results:

    http / http1.0

HTTP/1.1 400 Bad Request
Server: nginx
Date: Fri, 24 Mar 2017 15:25:07 GMT
Content-Type: text/html
Content-Length: 166
Connection: close

    Only type the first line, the rest will be the output of the telnet tool. In this case, it looks like the server is running NGINX. In reality it’s more complex than that though: on my Plesk machine, there’s a very elaborate setup that first processes PHP via Apache, and then serves those files via NGINX. So although the telnet tool is right in saying the file is served by NGINX, it is processed by Apache beforehand.

    Here’s what an Apache web server might print out:

    http / http1.0

HTTP/1.1 408 Request Timeout
Date: Fri, 24 Mar 2017 15:29:48 GMT
Server: Apache/2.4.6 (CentOS) PHP/5.4.16
Content-Length: 221
Connection: close
Content-Type: text/html; charset=iso-8859-1

    Best ask your hosting provider which web server they’re using on your site. Hope this helps!

  5. Hi Jay, this is just what I needed and works fine, however, web browsers are now reporting non secure content and blocking images etc. Removing the htaccess file makes it secure again! Any Idea what can be happening?

Leave a Comment!

This site uses Akismet to reduce spam. Learn how your comment data is processed.