本文介绍了HTTPS工作正常,但* .COM:443给出了一个400错误?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个网站注册(阿帕奇CentOS的),有超过连接任何问题的https,但是当我尝试调用一个页面中定义的端口443,即example.com:443我得到一个400错误。

I've got a site up (apache centos) that has no issues connecting over https but when I try to call a page with the 443 port defined ie example.com:443 I get a 400 error.

我看httpd.conf中,听443是注释。

I've looked at the httpd.conf and listen 443 is uncommented.

任何想法?

在此先感谢

推荐答案

的方法 HTTP :// WWW .example.com的是一样的去为<$c$c>http<$c$c>://www.example.com<$c$c>:80

The way http://www.example.com is the same as going for http://www.example.com:80

您会看到
  HTTPS ://www.example.com中等于<$c$c>https<$c$c>://www.example.com<$c$c>:443

You will see that https://www.example.com equals https://www.example.com:443

什么是可能发生在你的就是你正在尝试:

What is probably happening to you is you are trying:

<$c$c>http<$c$c>://www.example.com<$c$c>:443 (即,普通HTTP协议,但在443端口)。

http://www.example.com:443 (that is, plain HTTP protocol, but over the 443 port).

该网站的服务器期望 SSL加密数据 443端口。

The web server expects SSL-encrypted data on the 443 port.

当您使用 HTTP ://www.example.com中 :443 ,你告诉你的浏览器的讲纯HTTP ,以443中,通常是启用了SSL的服务器端口

When you use http://www.example.com:443, you're telling your browser to speak plain HTTP to 443, an usually SSL-enabled server port.

结果是未predictable。它最终取决于服务器。

The result is unpredictable. It ultimately depends on the server.

大多数服务器要么(1)杀了蝙蝠的权利或连接的(2)只给回 HTTP 400错误的请求回应,试图让你知道做错了什么(在 4XX 组错误,则表明客户端错误)。

Most servers will either (1) kill the connection right off the bat or (2) just give back a HTTP 400 Bad request response, trying to let you know you did something wrong (the 4xx group of errors indicates client errors).

这篇关于HTTPS工作正常,但* .COM:443给出了一个400错误?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-18 09:48