Summary: | [HTTP/2] The socket [*] associated with this connection has been closed. | ||
---|---|---|---|
Product: | Tomcat 8 | Reporter: | Selim Emre Toy <selimemretoy> |
Component: | Connectors | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | selimemretoy |
Priority: | P2 | ||
Version: | 8.5.61 | ||
Target Milestone: | ---- | ||
Hardware: | PC | ||
OS: | Linux |
Description
Selim Emre Toy
2021-01-03 16:26:29 UTC
There is insufficient information in this report to enable the issue to be reproduced. Reproduction requires: - a minimal (ideally single JSP or servlet) web application that reproduces the issue - the steps to reproduce the issue on clean install of the latest Tomcat 8.5.x release (or the latest release of any supported version) Hi Mark, Let me give an update. As I see, REST API working with also SSL. I have only having this issue in browser side. I think it's related to a browser data frame issue. The weird thing is, I also tried with overheadDataThreshold -1 value. But doesn't work still. Let me clear; Http + Browser -> working properly Http + REST API -> working properly Https + Browser -> doesn't work Https + REST API -> working properly Our browser application also using REST API in backend. Restoring the NEEDINFO state as the information requested in #1 has not been provided. There are multiple parameters related to managing HTTP/2 overhead. See http://tomcat.apache.org/tomcat-9.0-doc/config/http2.html Enabling HTTP/2 debug logging (see $CATALINA_BASE/conf/logging.properties) should enable you to identify any issues. Resolving this as invalid as all the indications so far is that this is inefficient framing on the client that Tomcat is detecting as a DoS attempt. Please use the users mailing list for further assistance. http://tomcat.apache.org/lists.html#tomcat-users This issue can be re-opened if on list discussions determine there is a bug here. |