From http://httpd.apache.org/docs/current/mod/mod_rewrite.html ornext|OR (or next condition) Use this to combine rule conditions with a local OR instead of the implicit AND. Typical example: RewriteCond %{REMOTE_HOST} ^host1 [OR] RewriteCond %{REMOTE_HOST} ^host2 [OR] RewriteCond %{REMOTE_HOST} ^host3 RewriteRule …some special stuff for any of these hosts…
The below answer could potentially cause an infinite redirect loop… Here, this one redirects everything after the domain name on the URL to the exact same copy on the new domain URL: RewriteEngine on RewriteRule ^(.*)$ http://www.newdomain.com/ [R=301,L] www.example.net/somepage.html?var=foo redirects to: www.newdomain.com
Try this in your .htaccess file (inside the web directory): <IfModule mod_rewrite.c> Options +FollowSymlinks RewriteEngine On # Explicitly disable rewriting for front controllers RewriteRule ^app_dev.php – [L] RewriteRule ^app.php – [L] RewriteCond %{REQUEST_FILENAME} !-f # Change below before deploying to production #RewriteRule ^(.*)$ /app.php [QSA,L] RewriteRule ^(.*)$ /app_dev.php [QSA,L] </IfModule>
I had a similar problem, and for me it was about the logged in user not having privileges so instead of service apache2 restart I had to do sudo service apache2 restart
figured it out… apparently I can do this: SSLProxyEngine On RequestHeader set Front-End-Https “On” ProxyPass / https://win.acme.com/ ProxyPassReverse / https://win.acme.com/ CacheDisable * and it works just fine! [the solution came from mikeg’s posting on 3cx.org]
From http://www.webconfs.com/how-to-redirect-a-webpage.php I’d say you can use the following configuration Don’t redirect subfolders/files (as you wanted): www.example.com/demo/ -> www.newexampledomain.com Options +FollowSymLinks RewriteEngine on RewriteRule (.*) http://www.newdomain.com/ [R=301,L] Redirect to subfolders/files: www.example.com/demo/ -> www.newexampledomain.com/demo/ Options +FollowSymLinks RewriteEngine on RewriteRule (.*) http://www.newdomain.com/$1 [R=301,L]
The No input file specified is a message you are presented with because of the implementation of PHP on your server, which in this case indicates a CGI implementation (can be verified with phpinfo()). Now, to properly explain this, you need to have some basic understanding on how your system works with URL’s. Based on … Read more
That is not possible. You need to have a ErrorDocument directive for each status code you want to handle differently than with the default error handler.
This is about Apache content negotiation. A MultiViews search is where the server does an implicit filename pattern match, and choose from amongst the results. For example, if you have a file called configuration.php (or other extension) in root folder and you set up a rule in your htaccess for a virtual folder called configuration/ … Read more
Try setting: “AllowOverride All”.