nginx redirects to the same url












0














I configured nginx as the following code



ssl_certificate  example.crt;
ssl_certificate_key example.key;

server {
listen 80;
server_name www.example.com example.com;
return 301 https://example.com$request_uri;
}

server {
listen 443 ssl;
server_name example.com;
return 200 hello;
}


and I expect to get 200 for curl -I https://example.com but it gives me 301



curl -I http://example.com => HTTP/1.1 301 Moved Permanently
location===https://example.com

curl -I https://example.com => HTTP/2 301
location===https://example.com

curl -I https://example.com/asdasd => HTTP/2 301
location===https://example.com/asdasd


Any help would be appreciated. thanks in advance.










share|improve this question
























  • The server configuration is not consistent with the results you are seeing. View the configuration using nginx -T. Do you have anything in front of the server and have you restarted Nginx since changing the configuration? Check the access logs to ensure that this server is the one that's responding.
    – Richard Smith
    Nov 14 '18 at 9:22










  • I haven't changed nginx.conf, yes I restart it whenever I change the config, and access.log is ok, I noticed that it always uses the first server block configuration even for https requests
    – fingerpich
    Nov 14 '18 at 9:46












  • I'm sorry but that doesn't make sense - there must be something in front of this server block that is terminating the https connection - like cloudflare.
    – Richard Smith
    Nov 14 '18 at 9:53










  • but the cloudflarer is OK as well, Universal SSL Status : Active Certificate
    – fingerpich
    Nov 14 '18 at 10:10










  • What happens for https requests? how https://example.com/asdasd changes to https://example.com/asdasd?
    – fingerpich
    Nov 14 '18 at 10:24
















0














I configured nginx as the following code



ssl_certificate  example.crt;
ssl_certificate_key example.key;

server {
listen 80;
server_name www.example.com example.com;
return 301 https://example.com$request_uri;
}

server {
listen 443 ssl;
server_name example.com;
return 200 hello;
}


and I expect to get 200 for curl -I https://example.com but it gives me 301



curl -I http://example.com => HTTP/1.1 301 Moved Permanently
location===https://example.com

curl -I https://example.com => HTTP/2 301
location===https://example.com

curl -I https://example.com/asdasd => HTTP/2 301
location===https://example.com/asdasd


Any help would be appreciated. thanks in advance.










share|improve this question
























  • The server configuration is not consistent with the results you are seeing. View the configuration using nginx -T. Do you have anything in front of the server and have you restarted Nginx since changing the configuration? Check the access logs to ensure that this server is the one that's responding.
    – Richard Smith
    Nov 14 '18 at 9:22










  • I haven't changed nginx.conf, yes I restart it whenever I change the config, and access.log is ok, I noticed that it always uses the first server block configuration even for https requests
    – fingerpich
    Nov 14 '18 at 9:46












  • I'm sorry but that doesn't make sense - there must be something in front of this server block that is terminating the https connection - like cloudflare.
    – Richard Smith
    Nov 14 '18 at 9:53










  • but the cloudflarer is OK as well, Universal SSL Status : Active Certificate
    – fingerpich
    Nov 14 '18 at 10:10










  • What happens for https requests? how https://example.com/asdasd changes to https://example.com/asdasd?
    – fingerpich
    Nov 14 '18 at 10:24














0












0








0







I configured nginx as the following code



ssl_certificate  example.crt;
ssl_certificate_key example.key;

server {
listen 80;
server_name www.example.com example.com;
return 301 https://example.com$request_uri;
}

server {
listen 443 ssl;
server_name example.com;
return 200 hello;
}


and I expect to get 200 for curl -I https://example.com but it gives me 301



curl -I http://example.com => HTTP/1.1 301 Moved Permanently
location===https://example.com

curl -I https://example.com => HTTP/2 301
location===https://example.com

curl -I https://example.com/asdasd => HTTP/2 301
location===https://example.com/asdasd


Any help would be appreciated. thanks in advance.










share|improve this question















I configured nginx as the following code



ssl_certificate  example.crt;
ssl_certificate_key example.key;

server {
listen 80;
server_name www.example.com example.com;
return 301 https://example.com$request_uri;
}

server {
listen 443 ssl;
server_name example.com;
return 200 hello;
}


and I expect to get 200 for curl -I https://example.com but it gives me 301



curl -I http://example.com => HTTP/1.1 301 Moved Permanently
location===https://example.com

curl -I https://example.com => HTTP/2 301
location===https://example.com

curl -I https://example.com/asdasd => HTTP/2 301
location===https://example.com/asdasd


Any help would be appreciated. thanks in advance.







nginx devops nginx-config






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 14 '18 at 9:16

























asked Nov 14 '18 at 0:11









fingerpich

3,55621221




3,55621221












  • The server configuration is not consistent with the results you are seeing. View the configuration using nginx -T. Do you have anything in front of the server and have you restarted Nginx since changing the configuration? Check the access logs to ensure that this server is the one that's responding.
    – Richard Smith
    Nov 14 '18 at 9:22










  • I haven't changed nginx.conf, yes I restart it whenever I change the config, and access.log is ok, I noticed that it always uses the first server block configuration even for https requests
    – fingerpich
    Nov 14 '18 at 9:46












  • I'm sorry but that doesn't make sense - there must be something in front of this server block that is terminating the https connection - like cloudflare.
    – Richard Smith
    Nov 14 '18 at 9:53










  • but the cloudflarer is OK as well, Universal SSL Status : Active Certificate
    – fingerpich
    Nov 14 '18 at 10:10










  • What happens for https requests? how https://example.com/asdasd changes to https://example.com/asdasd?
    – fingerpich
    Nov 14 '18 at 10:24


















  • The server configuration is not consistent with the results you are seeing. View the configuration using nginx -T. Do you have anything in front of the server and have you restarted Nginx since changing the configuration? Check the access logs to ensure that this server is the one that's responding.
    – Richard Smith
    Nov 14 '18 at 9:22










  • I haven't changed nginx.conf, yes I restart it whenever I change the config, and access.log is ok, I noticed that it always uses the first server block configuration even for https requests
    – fingerpich
    Nov 14 '18 at 9:46












  • I'm sorry but that doesn't make sense - there must be something in front of this server block that is terminating the https connection - like cloudflare.
    – Richard Smith
    Nov 14 '18 at 9:53










  • but the cloudflarer is OK as well, Universal SSL Status : Active Certificate
    – fingerpich
    Nov 14 '18 at 10:10










  • What happens for https requests? how https://example.com/asdasd changes to https://example.com/asdasd?
    – fingerpich
    Nov 14 '18 at 10:24
















The server configuration is not consistent with the results you are seeing. View the configuration using nginx -T. Do you have anything in front of the server and have you restarted Nginx since changing the configuration? Check the access logs to ensure that this server is the one that's responding.
– Richard Smith
Nov 14 '18 at 9:22




The server configuration is not consistent with the results you are seeing. View the configuration using nginx -T. Do you have anything in front of the server and have you restarted Nginx since changing the configuration? Check the access logs to ensure that this server is the one that's responding.
– Richard Smith
Nov 14 '18 at 9:22












I haven't changed nginx.conf, yes I restart it whenever I change the config, and access.log is ok, I noticed that it always uses the first server block configuration even for https requests
– fingerpich
Nov 14 '18 at 9:46






I haven't changed nginx.conf, yes I restart it whenever I change the config, and access.log is ok, I noticed that it always uses the first server block configuration even for https requests
– fingerpich
Nov 14 '18 at 9:46














I'm sorry but that doesn't make sense - there must be something in front of this server block that is terminating the https connection - like cloudflare.
– Richard Smith
Nov 14 '18 at 9:53




I'm sorry but that doesn't make sense - there must be something in front of this server block that is terminating the https connection - like cloudflare.
– Richard Smith
Nov 14 '18 at 9:53












but the cloudflarer is OK as well, Universal SSL Status : Active Certificate
– fingerpich
Nov 14 '18 at 10:10




but the cloudflarer is OK as well, Universal SSL Status : Active Certificate
– fingerpich
Nov 14 '18 at 10:10












What happens for https requests? how https://example.com/asdasd changes to https://example.com/asdasd?
– fingerpich
Nov 14 '18 at 10:24




What happens for https requests? how https://example.com/asdasd changes to https://example.com/asdasd?
– fingerpich
Nov 14 '18 at 10:24

















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%2f53291320%2fnginx-redirects-to-the-same-url%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













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.





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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53291320%2fnginx-redirects-to-the-same-url%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

鏡平學校

ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

Why https connections are so slow when debugging (stepping over) in Java?