blocks|key|1006977|text|如果您有这个侦听器：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1006978|++++<Listener+className="org.apache.catalina.core.AprLifecycleListener"+SSLEngine="on"/>|code-block|syntax|javascript|1006979|在您的server.xml上，删除它并尝试。如果使用APR连接器，则不能使用keystore。|1006980|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

If you have this listener:

<pre><code> &lt;Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on"/&gt;
</code></pre>

on your server.xml, remove it and try.
You can not use a keystore if you are using the APR connector

blocks|key|79868|text|对我来说，问题是传入一个比通常预期的更大的HTTP报头。我通过在maxHttpHeaderSize=中的Connector节点上设置server.xml“1048576”属性来解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|79869|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For me, the problem was passing in a larger than normally expected HTTP header. I resolved it by setting maxHttpHeaderSize="1048576" attribute on the Connector node in server.xml.

blocks|key|1007005|text|如果缓存的cookie太多，它就会破坏服务器(请求头的大小太大了！)清除cookie也可以解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1007006|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If there are too many cookies cached, it breaks the server (the size of a request header is too big!). Clearing the cookies can fix this issue as well.

blocks|key|79923|text|如果您不是意外地请求HTTPS协议而不是HTTP，请检查。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|79924|我忽略了我是在请求https://localhost:...而不是http://localhost:...，这导致了一条奇怪的消息。|offset|length|style|CODE|79925|entityMap^0|0|9|L|X|K|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|I|$]]

Check, if you are not accidentally requesting HTTPS protocol instead of HTTP.

I have overlooked that I was requesting <code>https://localhost:...</code> instead of <code>http://localhost:...</code> and it resulted to this weird message..

blocks|key|1007064|text|我有一个类似的问题，我发送一个POST请求(使用RESTClient插件的火狐)与数据在请求体，并收到相同的消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1007065|在我的例子中，之所以发生这种情况，是因为我试图在未配置HTTPS的本地tomcat实例中使用HTTPS协议。|1007066|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had a similar issue, I was sending a POST request (using RESTClient plugin for Firefox) with data in the request body and was receiving the same message.

In my case this happened because I was trying to use HTTPS protocol in a local tomcat instance where HTTPS was not configured.

blocks|key|2083821|text|当我试图打开https时，就会出现问题。我不使用SSL。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2083822|我是Tomcat+错误。|2083823|现在12/02/2017+Debian存储库的最新官方版本是Tomcat+8.0.14|2083824|解决方案是从官方网站下载并安装最新的Tomcat+8、8.5、9软件包，或者从jessie后台升级到最新的。|2083825|Debian+8|2083826|添加到/etc/apt/sources.list+.列表|2083827|deb+http://ftp.debian.org/debian+jessie-backports+main|code-block|syntax|javascript|2083828|然后从jessie-backports更新并安装Tomcat。|2083829|sudo+apt-get+update+&&+sudo+apt-get+-t+jessie-backports+install+tomcat8|2083830|entityMap|0|LINK|mutability|MUTABLE|url|https://bz.apache.org/bugzilla/show_bug.cgi?id=60581^0|6|5|0|9|2|0|0|U|D|0|I|E|1H|1|0|0|8|0|0|S|0|0|0|V|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|19|8|@]|D|@$9|1A|A|1B|1|1C]]|E|$]]|$1|H|3|I|5|6|7|1D|8|@$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1G|8|@$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|1L|8|@$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|1O|8|@$9|1P|A|1Q|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|R|7|1R|8|@]|D|@]|E|$S|T]]|$1|U|3|V|5|6|7|1S|8|@$9|1T|A|1U|B|C]]|D|@]|E|$]]|$1|W|3|X|5|R|7|1V|8|@]|D|@]|E|$S|T]]|$1|Y|3|-4|5|6|7|1W|8|@]|D|@]|E|$]]]|Z|$10|$5|11|12|13|E|$14|15]]]]

My problem occurs when I try to open https. I don't use SSL.

It's Tomcat <a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=60581" rel="nofollow noreferrer">bug</a>.

Today 12/02/2017 newest official version from Debian repositories is Tomcat 8.0.14

Solution is to download from official site and install newest package of Tomcat 8, 8.5, 9 or upgrade to newest version(8.5.x) from jessie-backports
 
 

<h3>Debian 8</h3>

Add to /etc/apt/sources.list

<pre><code>deb http://ftp.debian.org/debian jessie-backports main
</code></pre>

Then update and install Tomcat from jessie-backports

<pre><code>sudo apt-get update &amp;&amp; sudo apt-get -t jessie-backports install tomcat8
</code></pre>

blocks|key|1007088|text|我试过以上所有的方法，但对我来说都没有用。然后，我更改了tomcat端口号，包括HTTP/1.1和Tomcat管理端口，并得到了解决。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1007089|我看到上面的其他解决方案对人们有用，但是如果上面的任何一种方法都不起作用的话，尝试一下这个方法是值得的。|1007090|谢谢大家！|1007091|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I tried all of the above, nothing worked for me.
Then I changed tomcat port numbers both HTTP/1.1 and Tomcat admin port and it got solved.

I see other solutions above worked for the people but it is worth to try this one if any of the above doesn't work.

Thanks everyone!

blocks|key|2083759|text|在我们的例子中，错误的发生是因为我们的应用程序中有一个自定义的filter，它对其他url执行HttpServletResponse+sendRedirect()。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2083760|由于某些原因，重定向没有关闭连接的keep-alive状态，因此出现超时异常。|2083761|我们使用Tomcat文档进行检查，当我们通过将maxKeepAliveRequests的值设置为1来禁用它时，错误将停止显示。|2083762|目前，我们还没有解决这个错误的实际解决方案。|2083763|entityMap|0|LINK|mutability|MUTABLE|url|https://tomcat.apache.org/tomcat-7.0-doc/config/http.html^0|V|6|1B|Y|0|H|A|0|N|K|1C|1|4|8|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@$9|16|A|17|1|18]]|E|$]]|$1|J|3|K|5|6|7|19|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]]]

In our case it turned out that the error happened because we have a custom <code>filter</code> in our application which does <code>HttpServletResponse sendRedirect()</code> to other url.

For some reason, the redirection is not closing the <code>keep-alive</code> status of the connection, hence the timeout exception.

We checked with <a href="https://tomcat.apache.org/tomcat-7.0-doc/config/http.html" rel="nofollow">Tomcat Docs</a> and when we disabled the <code>maxKeepAliveRequests</code> by setting it's value to <code>1</code> and the error stopped showing up.

For now we do not have the actual solution to the error.

blocks|key|2083891|text|当我在Debian+10中使用Tomcat作为应用服务器时，我遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2083892|问题是，在我使用http在浏览器中调用应用程序时，应用程序已经将定义为它的默认协议。因此，当我尝试运行应用程序时，我在日志文件中得到了以下错误：|2083893|org.apache.coyote.http11.AbstractHttp11Processor+process
INFO:+Error+parsing+HTTP+request+header
+Note:+further+occurrences+of+HTTP+header+parsing+errors+will+be+logged+at+DEBUG+level.|code-block|syntax|javascript|2083894|不过，我尝试在浏览器中使用https协议，但它没有连接，引发错误：|2083895|，这是我怎么解决的，|2083896|您需要一个证书来为应用程序设置https协议。我首先必须为应用程序创建一个密钥库文件，更像是https协议的自签名证书：|2083897|sudo+keytool+-genkey+-keyalg+RSA+-alias+tomcat+-keystore+/usr/share/tomcat.keystore|2083898|备注：您需要在服务器上安装才能做到这一点。可以使用sudo+apt+install+default-jdk安装Java。|CODE|2083899|接下来，我在Tomcat服务器配置文件()中为应用程序添加了一个https+Tomcat服务器连接器：|2083900|sudo+nano+/opt/tomcat/conf/server.xml|2083901|将以下内容添加到应用程序的配置中。注意，指定了密钥库文件位置和密码。此外，还为https协议定义了一个端口，它不同于http协议的端口：|2083902|<Connector+protocol="org.apache.coyote.http11.Http11Protocol"
+++++++++++port="8443"+maxThreads="200"+scheme="https"
+++++++++++secure="true"+SSLEnabled="true"
+++++++++++keystoreFile="/usr/share/tomcat.keystore"
+++++++++++keystorePass="my-password"
+++++++++++clientAuth="false"+sslProtocol="TLS"
+++++++++++URIEncoding="UTF-8"
+++++++++++compression="force"
+++++++++++compressableMimeType="text/html,text/xml,text/plain,text/javascript,text/css"/>|2083903|因此，应用程序的完整服务器配置在Tomcat服务器配置文件(/opt/tomcat/conf/server.xml)中如下所示：|2083904|<Service+name="my-application">
++<Connector+protocol="org.apache.coyote.http11.Http11Protocol"
+++++++++++++port="8443"+maxThreads="200"+scheme="https"
+++++++++++++secure="true"+SSLEnabled="true"
+++++++++++++keystoreFile="/usr/share/tomcat.keystore"
+++++++++++++keystorePass="my-password"
+++++++++++++clientAuth="false"+sslProtocol="TLS"
+++++++++++++URIEncoding="UTF-8"
+++++++++++++compression="force"
+++++++++++++compressableMimeType="text/html,text/xml,text/plain,text/javascript,text/css"/>

++<Connector+port="8009"+protocol="HTTP/1.1"
+++++++++++++connectionTimeout="20000"
+++++++++++++redirectPort="8443"+/>

++<Engine+name="my-application"+defaultHost="localhost">
+++++<Realm+className="org.apache.catalina.realm.LockOutRealm">
++++++++<Realm+className="org.apache.catalina.realm.UserDatabaseRealm"
+++++++++++++resourceName="UserDatabase"/>
++++</Realm>

++++<Host+name="localhost"++appBase="webapps"
++++++++++unpackWARs="true"+autoDeploy="true">

++++++++<Valve+className="org.apache.catalina.valves.AccessLogValve"+directory="logs"
+++++++++++++prefix="localhost_access_log"+suffix=".txt"
+++++++++++++pattern="%25h+%25l+%25u+%25t+&quot;%25r&quot;+%25s+%25b"+/>

++++</Host>
++</Engine>
</Service>|2083905|这一次，当我尝试使用以下方法从浏览器访问应用程序时：|2083906|https://my-server-ip-address:https-port|2083907|就我而言，它是：|2083908|https:35.123.45.6:8443|2083909|效果很好。虽然，我不得不接受一个警告，这增加了一个网站的安全例外，因为使用的证书是自签名的。|2083910|就这样。|2083911|我希望这对有帮助|2083912|entityMap^0|3|9|F|6|0|8|4|0|0|D|5|0|0|A|0|F|5|11|3|1A|5|0|0|0|2|P|S|0|K|C|0|0|N|3|13|5|1M|4|0|0|G|6|U|R|0|0|0|0|0|0|0|0|0|5|0^^$0|@$1|2|3|4|5|6|7|1P|8|@$9|1Q|A|1R|B|C]|$9|1S|A|1T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1U|8|@$9|1V|A|1W|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|1X|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1Y|8|@$9|1Z|A|20|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|21|8|@$9|22|A|23|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|24|8|@$9|25|A|26|B|C]|$9|27|A|28|B|C]|$9|29|A|2A|B|C]]|D|@]|E|$]]|$1|S|3|T|5|J|7|2B|8|@]|D|@]|E|$K|L]]|$1|U|3|V|5|6|7|2C|8|@$9|2D|A|2E|B|C]|$9|2F|A|2G|B|W]]|D|@]|E|$]]|$1|X|3|Y|5|6|7|2H|8|@$9|2I|A|2J|B|C]]|D|@]|E|$]]|$1|Z|3|10|5|J|7|2K|8|@]|D|@]|E|$K|L]]|$1|11|3|12|5|6|7|2L|8|@$9|2M|A|2N|B|C]|$9|2O|A|2P|B|C]|$9|2Q|A|2R|B|C]]|D|@]|E|$]]|$1|13|3|14|5|J|7|2S|8|@]|D|@]|E|$K|L]]|$1|15|3|16|5|6|7|2T|8|@$9|2U|A|2V|B|C]|$9|2W|A|2X|B|W]]|D|@]|E|$]]|$1|17|3|18|5|J|7|2Y|8|@]|D|@]|E|$K|L]]|$1|19|3|1A|5|6|7|2Z|8|@]|D|@]|E|$]]|$1|1B|3|1C|5|J|7|30|8|@]|D|@]|E|$K|L]]|$1|1D|3|1E|5|6|7|31|8|@]|D|@]|E|$]]|$1|1F|3|1G|5|J|7|32|8|@]|D|@]|E|$K|L]]|$1|1H|3|1I|5|6|7|33|8|@]|D|@]|E|$]]|$1|1J|3|1K|5|6|7|34|8|@]|D|@]|E|$]]|$1|1L|3|1M|5|6|7|35|8|@$9|36|A|37|B|C]]|D|@]|E|$]]|$1|1N|3|-4|5|6|7|38|8|@]|D|@]|E|$]]]|1O|$]]

I had this issue when working on a Java Project in Debian 10 with Tomcat as the application server.
The issue was that the application already had https defined as it's default protocol while I was using http to call the application in the browser. So when I try running the application I get this error in my log file:
<pre><code>org.apache.coyote.http11.AbstractHttp11Processor process
INFO: Error parsing HTTP request header
 Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
</code></pre>
I however tried using the https protocol in the browser but it didn't connect throwing the error:
Here's how I solved it:
You need a certificate to setup the https protocol for the application. I first had to create a keystore file for the application, more like a self-signed certificate for the https protocol:
<pre><code>sudo keytool -genkey -keyalg RSA -alias tomcat -keystore /usr/share/tomcat.keystore
</code></pre>
Note: You need to have Java installed on the server to be able to do this. Java can be installed using <code>sudo apt install default-jdk</code>.
Next, I added a https Tomcat server connector for the application in the Tomcat server configuration file (<code>/opt/tomcat/conf/server.xml</code>):
<pre><code>sudo nano /opt/tomcat/conf/server.xml
</code></pre>
Add the following to the configuration of the application. Notice that the keystore file location and password are specified. Also a port for the https protocol is defined, which is different from the port for the http protocol:
<pre><code>&lt;Connector protocol=&quot;org.apache.coyote.http11.Http11Protocol&quot;
 port=&quot;8443&quot; maxThreads=&quot;200&quot; scheme=&quot;https&quot;
 secure=&quot;true&quot; SSLEnabled=&quot;true&quot;
 keystoreFile=&quot;/usr/share/tomcat.keystore&quot;
 keystorePass=&quot;my-password&quot;
 clientAuth=&quot;false&quot; sslProtocol=&quot;TLS&quot;
 URIEncoding=&quot;UTF-8&quot;
 compression=&quot;force&quot;
 compressableMimeType=&quot;text/html,text/xml,text/plain,text/javascript,text/css&quot;/&gt;
</code></pre>
So the full server configuration for the application looked liked this in the Tomcat server configuration file (<code>/opt/tomcat/conf/server.xml</code>):
<pre><code>&lt;Service name=&quot;my-application&quot;&gt;
 &lt;Connector protocol=&quot;org.apache.coyote.http11.Http11Protocol&quot;
 port=&quot;8443&quot; maxThreads=&quot;200&quot; scheme=&quot;https&quot;
 secure=&quot;true&quot; SSLEnabled=&quot;true&quot;
 keystoreFile=&quot;/usr/share/tomcat.keystore&quot;
 keystorePass=&quot;my-password&quot;
 clientAuth=&quot;false&quot; sslProtocol=&quot;TLS&quot;
 URIEncoding=&quot;UTF-8&quot;
 compression=&quot;force&quot;
 compressableMimeType=&quot;text/html,text/xml,text/plain,text/javascript,text/css&quot;/&gt;

 &lt;Connector port=&quot;8009&quot; protocol=&quot;HTTP/1.1&quot;
 connectionTimeout=&quot;20000&quot;
 redirectPort=&quot;8443&quot; /&gt;

 &lt;Engine name=&quot;my-application&quot; defaultHost=&quot;localhost&quot;&gt;
 &lt;Realm className=&quot;org.apache.catalina.realm.LockOutRealm&quot;&gt;
 &lt;Realm className=&quot;org.apache.catalina.realm.UserDatabaseRealm&quot;
 resourceName=&quot;UserDatabase&quot;/&gt;
 &lt;/Realm&gt;

 &lt;Host name=&quot;localhost&quot; appBase=&quot;webapps&quot;
 unpackWARs=&quot;true&quot; autoDeploy=&quot;true&quot;&gt;

 &lt;Valve className=&quot;org.apache.catalina.valves.AccessLogValve&quot; directory=&quot;logs&quot;
 prefix=&quot;localhost_access_log&quot; suffix=&quot;.txt&quot;
 pattern=&quot;%h %l %u %t &amp;quot;%r&amp;quot; %s %b&quot; /&gt;

 &lt;/Host&gt;
 &lt;/Engine&gt;
&lt;/Service&gt;
</code></pre>
This time when I tried accessing the application from the browser using:
<pre><code>https://my-server-ip-address:https-port
</code></pre>
In my case it was:
<pre><code>https:35.123.45.6:8443
</code></pre>
it worked fine. Although, I had to accept a warning which added a security exception for the website since the certificate used is a self-signed one.
That's all.
I hope this helps

blocks|key|1007171|text|如果不想升级tomcat，请在catalina.properties中添加这一行|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1007172|tomcat.util.http.parser.HttpParser.requestTargetAllow=%7C{}|code-block|syntax|javascript|1007173|它对我有用，8109.html|1007174|entityMap|0|LINK|mutability|MUTABLE|url|http://www.zhoulujun.cn/zhoulujun/html/java/tomcat/2018_0508_8109.html^0|F|J|0|0|6|9|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

If you don't want to upgrade your tomcat,
Add this line in your <code>catalina.properties</code>

<pre><code>tomcat.util.http.parser.HttpParser.requestTargetAllow=|{}
</code></pre>

It works for me
<a href="http://www.zhoulujun.cn/zhoulujun/html/java/tomcat/2018_0508_8109.html" rel="nofollow noreferrer">http://www.zhoulujun.cn/zhoulujun/html/java/tomcat/2018_0508_8109.html</a>

I use Tomcat 7.0.43 with a websocket application. My app works fine in Tomcat 7.0.42 but with 43 I get the following output when I try to access my server on websockets:

<pre><code>Sep 16, 2013 3:08:34 AM org.apache.coyote.http11.AbstractHttp11Processor process
INFO: Error parsing HTTP request header
 Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
</code></pre>

My browser console shows the following: 

<pre><code>WebSocket connection to 'ws://www.testapp.com/socket/notification/848df2e62fcf93e1b3?X-Atmosphere-tracking-i…Date=0&amp;Content-Type=application/json;%20charset=UTF-8&amp;X-atmo-protocol=true' failed: Unrecognized frame opcode: 5 
</code></pre>

Here is the access log for that request: 

<pre><code>"GET /socket/notification/848df2e62fcf93e1b3?X-Atmosphere-tracking-id=0&amp;X-Atmosphere-Framework=2.0.2-javascript&amp;X-Atmosphere-Transport=websocket&amp;X-Atmosphere-TrackMessageSize=true&amp;X-Cache-Date=0&amp;Content-Type=application/json;%20charset=UTF-8&amp;X-atmo-protocol=true HTTP/1.1"
</code></pre>

What has changed in Tomcat 7.0.43? What do I have to change?

Tomcat 7.0.43 "INFO: Error parsing HTTP request header"

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我在websocket应用程序中使用Tomcat 7.0.43。我的应用程序在Tomcat 7.0.42中运行良好，但是使用43时，当我试图访问websockets上的服务器时，我得到了以下输出：Sep 16, 2013 3:08:34 AM org.apache.coyote.http11.AbstractHttp11Processor processINFO: Error parsing HT

问Tomcat 7.0.43“信息:解析HTTP请求头错误”
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Tomcat 7.0.43“信息:解析HTTP请求头错误”EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Tomcat 7.0.43“信息:解析HTTP请求头错误”
EN