RewriteCond %{SCRIPT_FILENAME} -f RewriteRule path/downloads/(.*) path/downloads/getdownload. Php? L Still shows downloads/index.
Php in URL, but serves /downloads/getdownload. Php content, AND makes sure it's a file. (note: my .
Htaccess file is in the top level of my test site. ) If you want to put it into /downloads/ you can delete "path/downloads/" from both sides of the rule.
This seems to be doing the opposite of what I need--I need the file to not exist, but rather exist in the downloads directory in which case the script getdownload. Php (not in downloads) is rewritten to. – CMC Mar 9 at 18:36 If I understand you right, then all you would need to do is remove /downloads/ from the last part of the rule.At that point Apache should say, "visitor is requesting a file (which exists) in path/downloads/, therefore I'll point them to path/getdownload.
Php". With or without the Cond above, you'll get a 404 if the file doesn't exist in /downloads/. By adding the Cond, the Rule is only fired if a file truely does exists in /downloads/ - essentially killing page calls one script sooner.
– Dawson Mar 9 at 19:26 RewriteRule path/downloads/(.*) path/getdownload. Php? L – Dawson Mar 10 at 6:51.
I'm attempting to get a RewriteCond/RewriteRule pair working, which results in a 404 error unless I uncomment the RewriteCond, in which case everything is redirected. The idea is, if the file exists in the downloads directory to send the user to the getdownload. Php script, which distributes the download, assuming they have permission.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.