Hello chaps, thanks for the responses.
@hoopycat, I've created a number of different sized randomly generated files that you can try and download yourself:
- 5GB -
http://www.livefreedietravelling.com/testfile5gb.tar.gz- 3GB -
http://www.livefreedietravelling.com/testfile3gb.tar.gz- 1GB -
http://www.livefreedietravelling.com/testfile1gb.tar.gz- 512MB -
http://www.livefreedietravelling.com/testfile512mb.tar.gz@Main Street James, I can download the file via FTP but this is not a suitable solution for my situation. Ideally I would need WGET or browser download as eventually I'd need visitors to download large files from the front-end.
I changed the error logging level to notice and got the following back (I modified error_log /var/log/nginx/error.log warn; to display notices), I'm not sure if there is a deeper level of error reporting that is relevant to this issue? If so, how would I go about doing it?:
Code:
2013/05/19 08:40:11 [notice] 10452#0: *15 "/wp-admin$" does not match "/testfile5gb.tar.gz", client: 198.143.34.33, server: livefreedietravelling.com, request: "GET /testfile5gb.tar.gz HTTP/1.1", host: "www.livefreedietravelling.com"
2013/05/19 08:40:11 [notice] 10452#0: *15 "^(TRACE|DELETE|TRACK)" does not match "GET", client: 198.143.34.33, server: livefreedietravelling.com, request: "GET /testfile5gb.tar.gz HTTP/1.1", host: "www.livefreedietravelling.com"
2013/05/19 08:40:11 [notice] 10452#0: *15 "wordpress_logged_in_" does not match "", client: 198.143.34.33, server: livefreedietravelling.com, request: "GET /testfile5gb.tar.gz HTTP/1.1", host: "www.livefreedietravelling.com"
2013/05/19 08:40:11 [notice] 10452#0: *15 "^loggedout=true" does not match "", client: 198.143.34.33, server: livefreedietravelling.com, request: "GET /testfile5gb.tar.gz HTTP/1.1", host: "www.livefreedietravelling.com"
It seems like when I'm logged in I can download the file. Maybe it has something to do with the Better WP Security rules at the bottom of my nginx .conf file? I'm lacking some knowledge on NGINX rewrite rules and even Better WP Security itself so any help here would also be greatly appreciated... It just seems odd that only large files are affected, yet smaller files of the same extension can be downloaded without a problem.
Code:
# BEGIN Better WP Security
set $susquery 0;
set $rule_2 0;
set $rule_3 0;
if ($request_method ~* "^(TRACE|DELETE|TRACK)"){ return 403; }
location /wp-comments-post.php {
valid_referers jetpack.wordpress.com/jetpack-comment/ *.livefreedietravelling.com;
set $rule_0 0;
if ($request_method ~ "POST"){ set $rule_0 1$rule_0; }
if ($invalid_referer) { set $rule_0 2$rule_0; }
if ($http_user_agent ~ "^$"){ set $rule_0 3$rule_0; }
if ($rule_0 = "3210") { return 403; }
} if ($http_cookie !~* "wordpress_logged_in_" ) {
set $susquery 2$susquery;
set $rule_2 1;
set $rule_3 1;
}
if ($args !~ "^loggedout=true") { set $susquery 3$susquery; }
# END Better WP Security