Drupal site keeps on redirecting
Base URL is already set to in the settings.php file
$base_url = 'https://<site_name>.com.au";
But when accesssing it thru www.<site_name>.com.au
it seems that it will have a redirect loop.
Here's the .htaccess Rewrite:
RewriteCond %{HTTP_HOST} .
RewriteCond %{HTTP_HOST} www. [NC]
RewriteRule ^ http%{ENV:protossl}://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
.htaccess redirect drupal drupal-7
add a comment |
Base URL is already set to in the settings.php file
$base_url = 'https://<site_name>.com.au";
But when accesssing it thru www.<site_name>.com.au
it seems that it will have a redirect loop.
Here's the .htaccess Rewrite:
RewriteCond %{HTTP_HOST} .
RewriteCond %{HTTP_HOST} www. [NC]
RewriteRule ^ http%{ENV:protossl}://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
.htaccess redirect drupal drupal-7
What's happen if you remove custom rewrites into .htaccess (restart apache after it) and add to settings.php$conf['HTTPS'] = true;
?
– Fky
Nov 13 at 13:29
add a comment |
Base URL is already set to in the settings.php file
$base_url = 'https://<site_name>.com.au";
But when accesssing it thru www.<site_name>.com.au
it seems that it will have a redirect loop.
Here's the .htaccess Rewrite:
RewriteCond %{HTTP_HOST} .
RewriteCond %{HTTP_HOST} www. [NC]
RewriteRule ^ http%{ENV:protossl}://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
.htaccess redirect drupal drupal-7
Base URL is already set to in the settings.php file
$base_url = 'https://<site_name>.com.au";
But when accesssing it thru www.<site_name>.com.au
it seems that it will have a redirect loop.
Here's the .htaccess Rewrite:
RewriteCond %{HTTP_HOST} .
RewriteCond %{HTTP_HOST} www. [NC]
RewriteRule ^ http%{ENV:protossl}://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
.htaccess redirect drupal drupal-7
.htaccess redirect drupal drupal-7
asked Nov 12 at 3:05
Ronald
77331119
77331119
What's happen if you remove custom rewrites into .htaccess (restart apache after it) and add to settings.php$conf['HTTPS'] = true;
?
– Fky
Nov 13 at 13:29
add a comment |
What's happen if you remove custom rewrites into .htaccess (restart apache after it) and add to settings.php$conf['HTTPS'] = true;
?
– Fky
Nov 13 at 13:29
What's happen if you remove custom rewrites into .htaccess (restart apache after it) and add to settings.php
$conf['HTTPS'] = true;
?– Fky
Nov 13 at 13:29
What's happen if you remove custom rewrites into .htaccess (restart apache after it) and add to settings.php
$conf['HTTPS'] = true;
?– Fky
Nov 13 at 13:29
add a comment |
1 Answer
1
active
oldest
votes
When enforcing or stripping www, to avoid a bounce between HTTP and HTTPS, you should also uncomment the following in the .htaccess file:
RewriteRule ^ - [E=protossl]
RewriteCond %{HTTPS} on
RewriteRule ^ - [E=protossl:s]
The comments in the default .htaccess file define the above lines in function as such:
Set "protossl" to "s" if we were accessed via https://. This is used later
if you enable "www." stripping or enforcement, in order to ensure that
you don't bounce between http and https.
If you're adding the lines manually, make sure they precede your re-write, but come after
<IfModule mod_rewrite.c>
RewriteEngine on
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53255473%2fdrupal-site-keeps-on-redirecting%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
When enforcing or stripping www, to avoid a bounce between HTTP and HTTPS, you should also uncomment the following in the .htaccess file:
RewriteRule ^ - [E=protossl]
RewriteCond %{HTTPS} on
RewriteRule ^ - [E=protossl:s]
The comments in the default .htaccess file define the above lines in function as such:
Set "protossl" to "s" if we were accessed via https://. This is used later
if you enable "www." stripping or enforcement, in order to ensure that
you don't bounce between http and https.
If you're adding the lines manually, make sure they precede your re-write, but come after
<IfModule mod_rewrite.c>
RewriteEngine on
add a comment |
When enforcing or stripping www, to avoid a bounce between HTTP and HTTPS, you should also uncomment the following in the .htaccess file:
RewriteRule ^ - [E=protossl]
RewriteCond %{HTTPS} on
RewriteRule ^ - [E=protossl:s]
The comments in the default .htaccess file define the above lines in function as such:
Set "protossl" to "s" if we were accessed via https://. This is used later
if you enable "www." stripping or enforcement, in order to ensure that
you don't bounce between http and https.
If you're adding the lines manually, make sure they precede your re-write, but come after
<IfModule mod_rewrite.c>
RewriteEngine on
add a comment |
When enforcing or stripping www, to avoid a bounce between HTTP and HTTPS, you should also uncomment the following in the .htaccess file:
RewriteRule ^ - [E=protossl]
RewriteCond %{HTTPS} on
RewriteRule ^ - [E=protossl:s]
The comments in the default .htaccess file define the above lines in function as such:
Set "protossl" to "s" if we were accessed via https://. This is used later
if you enable "www." stripping or enforcement, in order to ensure that
you don't bounce between http and https.
If you're adding the lines manually, make sure they precede your re-write, but come after
<IfModule mod_rewrite.c>
RewriteEngine on
When enforcing or stripping www, to avoid a bounce between HTTP and HTTPS, you should also uncomment the following in the .htaccess file:
RewriteRule ^ - [E=protossl]
RewriteCond %{HTTPS} on
RewriteRule ^ - [E=protossl:s]
The comments in the default .htaccess file define the above lines in function as such:
Set "protossl" to "s" if we were accessed via https://. This is used later
if you enable "www." stripping or enforcement, in order to ensure that
you don't bounce between http and https.
If you're adding the lines manually, make sure they precede your re-write, but come after
<IfModule mod_rewrite.c>
RewriteEngine on
answered Nov 13 at 14:08
Bytech
364213
364213
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53255473%2fdrupal-site-keeps-on-redirecting%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What's happen if you remove custom rewrites into .htaccess (restart apache after it) and add to settings.php
$conf['HTTPS'] = true;
?– Fky
Nov 13 at 13:29