i'm using curently .htaccess to download files from my server with custom filename using RewriteEngine.
My rule looks like this:
RewriteRule ^d/([0-9]+)/(.*).jpg files/photo-$1.jpg
$1 is the file id that it is stored in db also.
Everything work fine but i want to update my db when the file is downloaded, i need a request to be sent to download.php?id=$1 when the rule is accesed.
Is there a way to do that with .htaccess and RewriteEngine ? I searched a lot but i didn't find any solution.
Any help will be highly appreciated, thanks.
i need a request to be sent to download.php?id=$1
Then rewrite the request to download.php?id=$1 instead of files/$2-$1.jpg. Your PHP script must then serve the actual image (ie. files/<name>-<id>.jpg) in the response, instead of directly rewriting to the file as you are doing currently.
Related
I would like when accessing the url https://www.italinea.com.br/uploads/jx5rufam7adfwd75pi6c.jpg, which is an existing file on the server, open the php file https://www.italinea.com.br/image.php.
Which htaccess rule do I use?
I tried to use:
RewriteRule ^(.+)\.jpg image.php [L,QSA]
But as it is an existing file, it opens the image and not the .php file
RewriteRule ^(.+)\.jpg image.php [L,QSA]
This is the right idea and should "work", although it could be simplified a bit. And it is rather generic, so matches every .jpg request.
If this is not working then either:
You have a conflict with other directives in the .htaccess file (the order of directives can be important).
You have a front-end proxy that is serving your static content. This is a problem if the URL being requested maps to a physical file as the application server (ie. .htaccess) is then completely bypassed.
If this is the case then see my answer to the following related question:
WordPress: can't achieve direct image access redirection via .htaccess
I'm going to try and make this as simple as possible, I have a POST form that sends information called $searchid, I want to redirect it to look like a directory
I want to take the following information: (Server, folder, file, post)
localhost/shorts/profile.php?searchid=12345
And I want to make it look like (Server, fakefolder(id), fakefolder(post))
localhost/id/12345/
Also, is there A way to incorporate the sitename, as all the htaccess ive seen before hasnt had it and it's been showing the entire path from C drive.
In htaccess in the root :
RewriteEngine on
RewriteRule ^id/([0-9]+)/?$ /sports/profile.php?searchid=$1 [NC,L]
This will rewrite
/id/numbers
to
/sports/profile.php?searchid=numbers
and allow you to access the page /sports/profile.php?searchid=numbers using the clean url /id/numbers .
right now my url looks like this:
http://domain.com/en/c/product%2C-product2%2C-product3/82
where last number is category numer.
And im trying to rewrite it and redirect user to url which should look this one:
http://domain.com/82/product-product2-product3
The clue is I want to hide "en/c/" part and clean url from commas and blank spaces. I'm completely green in rewriting.
Any ideas?
You can use these 2 rules in your root .htaccess for that:
RewriteEngine On
RewriteBase /
RewriteRule ^en/c/([^,\s]*)[,\s]+([^,\s]*)/(\d+)/?$ $3/$1$2 [NC,L,NE,R=302]
RewriteRule ^(en/c)/([^,\s]*)[,\s]+(.*)/(\d+)/?$ $1/$2$3/$4 [NC,L]
In order for this to work, we need to tell the server to internally redirect all requests for the URL "url1" to "url2.php". We want this to happen internally, because we don't want the URL in the browser's address bar to change.
To accomplish this, we need to first create a text document called ".htaccess" to contain our rules. It must be named exactly that (not ".htaccess.txt" or "rules.htaccess"). This would be placed in the root directory of the server (the same folder as "url2.php" in our example). There may already be an .htaccess file there, in which case we should edit that rather than overwrite it.
The .htaccess file is a configuration file for the server. If there are errors in the file, the server will display an error message (usually with an error code of "500").
If you are transferring the file to the server using FTP, you must make sure it is transferred using the ASCII mode, rather than BINARY. We use this file to perform 2 simple tasks in this instance - first, to tell Apache to turn on the rewrite engine, and second, to tell apache what rewriting rule we want it to use. We need to add the following to the file:
RewriteEngine On # Turn on the rewriting engine
RewriteRule ^url1/?$ url2.php [NC,L] # Handle requests for "url1"
How do I convert this .htaccess file to an app.yaml file?
Here is the .htaccess file:
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(?!.*?public).* index.php [QSA,L]
I need to do this to run an app using PHP on Google App Engine.
The reason I'm asking this question, is because Google specifically recommends a code example in their official documentation that is stored in Git Hub called Dr Edit. The Dr Edit code example has a .htaccess file, but no app.yaml file. And, in the READ ME file, the very first step for setting up the application, is to create a Google App Engine application. So I guess Google has provided a code example that insinuates it will run on Google App Engine, but it won't.
Supposedly Google is monitoring Stack Overflow for issues related to GAE, so I hope they read this.
Here is information about how to simulate Apache mod_rewrite $_GET['q'] routing for a PHP App Engine app, in case that's helpful.
As the name .htaccess implies, it can control access to a directory. The .htaccess files are read on every request. I guess that means that every HTTP request to the domain name must go through the .htaccess file. So it seems like the .htaccess file is like a gatekeeper. From Wikipedia, it seems that the .htaccess file can be used to block certain IP address from loading a web page.
The first line of the .htaccess file is: RewriteEngine On
That line of code: RewriteEngine is an Apache Directive which turns the Apache Rewriting Engine on or off.
So that .htaccess file is looking at every request, taking the request, then pushing out a different request.
It seems that the app.yaml file can not directly take one URL request, and push out a different request, BUT the app.yaml file can take a URL request, and then run a PHP script, that will change the request.
So, in the app.yaml file, the section that takes the URL, then redirects to a script, would look like this:
Catch the incoming URL requests and cause the mod_rewrite.php file to run.
- url: /Put the incoming URL you want to monitor, catch and redirect here
script: mod_rewrite.php
Redirect URL requests with app.yaml
The second line of the .htaccess file is:
RewriteCond %{REQUEST_FILENAME} !-f
This is a test, looking for a match in the incoming URL request. The -f at the end is for:
-f (is regular file) Treats the TestString as a pathname and tests whether or not it exists, and is a regular file.
Oh wait! There is an exclamation point in front of it. That's probably a test for logical not. So, if it's NOT a regular file?
Whatever that means. What is the difference between a regular file and everything else? What's an irregular file? lol idk. Anyway, it's looking for a file I guess.
From the Apache documentation, here is a quote:
Server-Variables: These are variables of the form %{ NAME_OF_VARIABLE
} where NAME_OF_VARIABLE can be a string taken from the following
list:
So that %{REQUEST_FILENAME} part of the second line is what Apache is calling a Server-Variable, and the specific Server-Variable is REQUEST_FILENAME.
Here is a quote from the Apache documentation:
REQUEST_FILENAME
The full local filesystem path to the file or script matching the request, if this has already been determined by the server at the time
REQUEST_FILENAME is referenced. Otherwise, such as when used in
virtual host context, the same value as REQUEST_URI. Depending on the
value of AcceptPathInfo, the server may have only used some leading
components of the REQUEST_URI to map the request to a file.
So I guess the .htaccess file is looking for something that looks like a path to files on your local computer?
Finally there is the Rewrite Rule Apache RewriteRule
What is the QSA at the end for? I guess it's called a flag, and:
Using the [QSA] flag causes the query strings to be combined
QSA seems to stand for Query String Append. If the incoming URL has a query string on the end of it, how do you want it dealt with?
The [L] prevents any further rewriting rules to be appended
Appache L rewrite flag
Appache Documentation QSA
The character (^) is called a caret. I don't know why it's used at the beginning. The syntax for the Appache Rewrite directive is:
RewriteRule pattern target [Flag1,Flag2,Flag3]
So the caret is part of the pattern being detected. That target is simply index.php. So it looks like if lots of different possible requests simply get routed back to the index.php file, which is the very first thing the application runs.
The asterisk at the end is probably a wildcard for any extension.
I think you're out of luck :-( Rewrite is an Apache module but AppEngine is based on Jetty, so you must redesign for that. You might be able to use one of the Bundled Servlets, Filters, and Handlers but none of them are a direct substitute for Apache Module mod_rewrite. Some people have used Apache as a front end before Jetty, but that is a clumsy approach. Sorry.
There are a way, via .htaccess to check if .css or .js has your own minified version (.min.css and .min.js, respectively) and redirect to this file, but need to have the same modified time.
For instance:
FILE MODIFIED TIME
/file.css 01-15-2014T19:28:12
/file.min.css 01-15-2014T19:28:12
/file.js 01-15-2014T19:28:12
/file.min.js 01-15-2014T19:27:47
My idea is: when someone access the file.css, the .htaccess will check if file.min.css is available and have the same modified time. If yes, it'll returned (via rewrite, redirect), instead of file.css.
But, if I access file.js, even existing the file.min.js, the .htaccess will return file.js because file.min.js is outdated (not have same date/hour).
Is it possible only with .htaccess?
For your first requirement try this rule in your DOCUMENT_ROOT/.htaccess file:
RewriteEngine On
# if a min version is available then load it
RewriteCond %{DOCUMENT_ROOT}/$1.min.$2 -f
RewriteRule ^([^.]+)\.(css|js)$ /$1.min.$2 [L,NC]
However mod_rewrite cannot check modification timestamp of your css/js files to make decision based on that. You might need to handle that in your server side code.