HTTP to jump to the HTTPS, why suddenly increase port 80?-CodePudding

I had websites such as www.abc.com will automatically jump to https://www.abc.com
IIS set according to this article https://blog.csdn.net/chenghuikai/article/details/56677938
Site running for several months are normal yesterday suddenly appeared the problem of more than ten minutes,
Is not normal to jump to https://www.abc.com but jump to cause the failure of website, https://www.abc.com:80
And through abc.com can automatically jump to https://abc.com
Our website is only a WAF, arguably WAF should not to modify the jump,
Ask friends teach encountered similar problems,

CodePudding user response:

Check the log file, find the cause of failed to jump, is in the server virus or network card

CodePudding user response:

reference 1/f, xiaoxiang dream response:

check log files, is to find the cause of failed to jump, servers or network virus caton

IIS log seen it all pretty normal network caton should not lead to jump address change off
Is fine and normal directly via HTTPS access, jump failure seems not write log?

CodePudding user response:

refer to the second floor sword farmers reply:

Quote: reference 1/f, xiaoxiang dream response:

Check the log file, find the cause of failed to jump, isn't it servers or network virus caton

IIS log seen it all pretty normal network caton should not lead to jump address change off
Is fine and normal directly via HTTPS access, jump failure seems not write log?

That I can think of leaves:
1. The server install updates or other software, lead to parse configuration error, the website redirect the
2. On the server and deploy a web site, in 80 port conflicts are less likely to be blocked or port 80
3. The website domain name is generic parsing or hijacked, is black

CodePudding user response:

reference xiaoxiang dream reply: 3/f

Quote: refer to the second floor sword farmers reply:

Quote: reference 1/f, xiaoxiang dream response:

Check the log file, find the cause of failed to jump, isn't it servers or network virus caton

IIS log seen it all pretty normal network caton should not lead to jump address change off
Is fine and normal directly via HTTPS access, jump failure seems not write log?

That I can think of leaves:
1. The server install updates or other software, lead to parse configuration error, the website redirect the
2. On the server and deploy a web site, in 80 port conflicts are less likely to be blocked or port 80
3. The website domain name is generic parsing or hijacked, is the dark

Thank you for your patience,
1. The server and network didn't do any change
2. The deployment of a web site,
3. The site generic parsing or hijack how to check?

Thank you for

CodePudding user response:

Domain name resolution should not, when I pointed to the network address of the local host or jump to the HTTPS address with port 80

CodePudding user response:

It is 80

CodePudding user response:

refer to 6th floor lllomh response:

is 80 o

HTTPS port is 443, jump to 80 have a problem

CodePudding user response:

Depressed ah ah...

CodePudding user response:

Wrote a strong look at the jump of the domain name binding certificate in port configuration is consistent?

CodePudding user response:

reference dog son, 9/f, have the sun replies:

wrote a strong look at the jump of the domain name binding certificate in port configuration is consistent?

Binding certificate of port is 443 and has no problem there ten minutes on the day the question,
The day has been good, until now, well head ache

CodePudding user response:

Feeling is automatically jump this step has problem, the jump is specifies the port number 80?

CodePudding user response:

reference 11 floor billet response:

feeling is automatically jump this step has a problem, if jump specifies the port number 80,

https://blog.csdn.net/chenghuikai/article/details/56677938
Is set up according to the rewriting rules should be no problem

CodePudding user response:

The building Lord solved? I ran into this problem recently, URL rewriting with more than a year is good, this problem these days