Redirect non .onion to https but keep .onion as http?












0















I am adding a .onion address to my site and need to redirect regular traffic to https and .onion traffic to keep as http. I've got:



if ($scheme != "https") {
if ($host !~* ".onion$") { # error occurs here
return 301 https://$host$request_uri;
}
}


I get the following error:



nginx: [emerg] "if" directive is not allowed here in nginx.conf:22









share|improve this question

























  • You could use multiple server blocks instead and avoid the if statements.

    – Richard Smith
    Nov 23 '18 at 21:56











  • My server block in real life is reaaaaaally long. I don't want to have to duplicate all my location blocks, headers, etc....would be error prone.

    – Marissa Levy
    Nov 23 '18 at 21:59











  • Offload common configuration into a separate file and use an include statement.

    – Richard Smith
    Nov 23 '18 at 22:02
















0















I am adding a .onion address to my site and need to redirect regular traffic to https and .onion traffic to keep as http. I've got:



if ($scheme != "https") {
if ($host !~* ".onion$") { # error occurs here
return 301 https://$host$request_uri;
}
}


I get the following error:



nginx: [emerg] "if" directive is not allowed here in nginx.conf:22









share|improve this question

























  • You could use multiple server blocks instead and avoid the if statements.

    – Richard Smith
    Nov 23 '18 at 21:56











  • My server block in real life is reaaaaaally long. I don't want to have to duplicate all my location blocks, headers, etc....would be error prone.

    – Marissa Levy
    Nov 23 '18 at 21:59











  • Offload common configuration into a separate file and use an include statement.

    – Richard Smith
    Nov 23 '18 at 22:02














0












0








0


1






I am adding a .onion address to my site and need to redirect regular traffic to https and .onion traffic to keep as http. I've got:



if ($scheme != "https") {
if ($host !~* ".onion$") { # error occurs here
return 301 https://$host$request_uri;
}
}


I get the following error:



nginx: [emerg] "if" directive is not allowed here in nginx.conf:22









share|improve this question
















I am adding a .onion address to my site and need to redirect regular traffic to https and .onion traffic to keep as http. I've got:



if ($scheme != "https") {
if ($host !~* ".onion$") { # error occurs here
return 301 https://$host$request_uri;
}
}


I get the following error:



nginx: [emerg] "if" directive is not allowed here in nginx.conf:22






nginx tor






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 23 '18 at 21:43







Marissa Levy

















asked Nov 23 '18 at 21:28









Marissa LevyMarissa Levy

2771652103




2771652103













  • You could use multiple server blocks instead and avoid the if statements.

    – Richard Smith
    Nov 23 '18 at 21:56











  • My server block in real life is reaaaaaally long. I don't want to have to duplicate all my location blocks, headers, etc....would be error prone.

    – Marissa Levy
    Nov 23 '18 at 21:59











  • Offload common configuration into a separate file and use an include statement.

    – Richard Smith
    Nov 23 '18 at 22:02



















  • You could use multiple server blocks instead and avoid the if statements.

    – Richard Smith
    Nov 23 '18 at 21:56











  • My server block in real life is reaaaaaally long. I don't want to have to duplicate all my location blocks, headers, etc....would be error prone.

    – Marissa Levy
    Nov 23 '18 at 21:59











  • Offload common configuration into a separate file and use an include statement.

    – Richard Smith
    Nov 23 '18 at 22:02

















You could use multiple server blocks instead and avoid the if statements.

– Richard Smith
Nov 23 '18 at 21:56





You could use multiple server blocks instead and avoid the if statements.

– Richard Smith
Nov 23 '18 at 21:56













My server block in real life is reaaaaaally long. I don't want to have to duplicate all my location blocks, headers, etc....would be error prone.

– Marissa Levy
Nov 23 '18 at 21:59





My server block in real life is reaaaaaally long. I don't want to have to duplicate all my location blocks, headers, etc....would be error prone.

– Marissa Levy
Nov 23 '18 at 21:59













Offload common configuration into a separate file and use an include statement.

– Richard Smith
Nov 23 '18 at 22:02





Offload common configuration into a separate file and use an include statement.

– Richard Smith
Nov 23 '18 at 22:02












0






active

oldest

votes











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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53453122%2fredirect-non-onion-to-https-but-keep-onion-as-http%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53453122%2fredirect-non-onion-to-https-but-keep-onion-as-http%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Create new schema in PostgreSQL using DBeaver

Deepest pit of an array with Javascript: test on Codility

Costa Masnaga