Learn how to use and navigate the new features included in Bootstrap 4, the most popular HTML, CSS, and JavaScript framework for developing responsive, mobile-first websites.
mod_rewrite to https or http
I have a rewrite rule in my htaccess file that sends all traffic to https. I have a unique situation that requires one page in my site to not be redirected to https. How can I accomplish this.
This is the rule I am using to send everything to https.
However, I need this rule to go to http instead.
This is the rule I am using to send everything to https.
RewriteRule ^(.*)$ https://www.bumpum.com/$1 [R=301,L]
However, I need this rule to go to http instead.
RewriteRule ^/?fb/(.*)$ /social_redirects.php?sign_serial=$1 [QSA,NC,L]
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Not tested, but you could negate the request URI before the https rule:
Dan
RewriteCond %{REQUEST_URI} !^/?fb/(.*)$
RewriteRule ^(.*)$ https://www.bumpum.com/$1 [R=301,L]
Dan
Weird. It should of worked.
Anyway, add the full path to the second rule.
Anyway, add the full path to the second rule.
RewriteRule ^/?fb/(.*)$ http://www.bumpum.com/social_redirects.php?sign_serial=$1 [QSA,NC,L]
If I put it like this it still does not work. Still redirects all to https
If I put it like this it fails in the browser and says this webpage has a redirect loop.
RewriteRule ^(.*)$ https://www.bumpum.com/$1 [R=301,L]
RewriteRule ^/?fb/(.*)$ http://www.bumpum.com/social_redirects.php?sign_serial=$1 [QSA,NC,L]
If I put it like this it fails in the browser and says this webpage has a redirect loop.
RewriteRule ^/?fb/(.*)$ http://www.bumpum.com/social_redirects.php?sign_serial=$1 [QSA,NC,L]
RewriteRule ^(.*)$ https://www.bumpum.com/$1 [R=301,L]
Both rules have an L at the end, meaning they are the last rules used, if true.
So yes, this:
But reversing the order should produce correct results: if the page is of the form http://www.bumpum.com/fb/something then the first rule is applied and the next is ignored, if not then the second rule is applied.
Can you please try another browser? Maybe it's a caching issue.
So yes, this:
RewriteRule ^(.*)$ https://www.bumpum.com/$1 [R=301,L]
RewriteRule ^/?fb/(.*)$ http://www.bumpum.com/social_redirects.php?sign_serial=$1 [QSA,NC,L]
But reversing the order should produce correct results: if the page is of the form http://www.bumpum.com/fb/something then the first rule is applied and the next is ignored, if not then the second rule is applied.
Can you please try another browser? Maybe it's a caching issue.
I have now tried multiple browsers and multiple computers. I always get the same results.
If i put this first it comes back with a browser failure (redirect loop) Its like the L is not working at all.
I also tried it like this and it does not work either. I removed the L thinking it might move to the next rule but does not work. I tried every combination I can think of.
If i put this first it comes back with a browser failure (redirect loop) Its like the L is not working at all.
RewriteRule ^/?fb/(.*)$ http://www.bumpum.com/social_redirects.php?sign_serial=$1 [QSA,NC,L]
I also tried it like this and it does not work either. I removed the L thinking it might move to the next rule but does not work. I tried every combination I can think of.
RewriteRule ^(.*)$ https://www.bumpum.com/$1 [R=301]
RewriteRule ^/?fb/(.*)$ http://www.bumpum.com/social_redirects.php?sign_serial=$1 [QSA,NC,L]
In PHP you can detect HTTPS and use header("Location:...") to redirect the browser. You would want to be mindful of the risk of complex interaction between .htaccess and the PHP redirect.
http://php.net/manual/en/reserved.variables.server.php
http://php.net/manual/en/reserved.variables.server.php
I have a very similar problem to this one.
All traffic to a site must be https, so I rewrite all URLS to redirect to https.
BUT I have one URL which comes not from the browser but an embedded activeX control which must go directly to CGI. This does not work.
I'm still fiddling, so I'll keep you posted.
All traffic to a site must be https, so I rewrite all URLS to redirect to https.
BUT I have one URL which comes not from the browser but an embedded activeX control which must go directly to CGI. This does not work.
I'm still fiddling, so I'll keep you posted.
@ray - the reason I cannot use that is I am using NFC technology in my application to redirect to a social media ap and if I send it to https first it opens up a browser window and sends them to the site in the browser which is not what I want to do. If I use http: it sends them to my redirect page then the phone prompts the user to use their social ap to open and that is what I want to do. So I only need the one page to go to http: and all others to go to https: It will need to be done in the rewrite.
@Steve - I do not know how to implement what you are saying. If you could give me an example it would be greatly appreciated.
@Steve - I do not know how to implement what you are saying. If you could give me an example it would be greatly appreciated.
Well, you've got an "interesting" design here -- one that nobody else uses and now you can see why not :-) Here's an alternative idea:
Get rid of the .htaccess and instead use a common script element at the top of all of your PHP web pages. Most web sites and web applications are designed this way - something that starts the session, connects to the database, loads the class definitions, etc. This PHP script can examine the URL it's using by looking in $_SERVER['PHP_SELF']. If the URL is the "magic one" that needs to be HTTP, no action occurs. Otherwise the script redirects with header("Location") to the HTTPS version. Your logic looks like this:
1. Am I running under HTTPS?
1.A. Yes, continue
2. Am I supposed to run under HTTP?
2.A. Yes, continue
3. header("Location...") // redirect to same REQUEST_URI but with HTTPS protocol.
Get rid of the .htaccess and instead use a common script element at the top of all of your PHP web pages. Most web sites and web applications are designed this way - something that starts the session, connects to the database, loads the class definitions, etc. This PHP script can examine the URL it's using by looking in $_SERVER['PHP_SELF']. If the URL is the "magic one" that needs to be HTTP, no action occurs. Otherwise the script redirects with header("Location") to the HTTPS version. Your logic looks like this:
1. Am I running under HTTPS?
1.A. Yes, continue
2. Am I supposed to run under HTTP?
2.A. Yes, continue
3. header("Location...") // redirect to same REQUEST_URI but with HTTPS protocol.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial