https://issues.apache.org/bugzilla/show_bug.cgi?id=56555
--- Comment #2 from Brett <lee.br...@gmail.com> --- Thanks for the quick reply. So is it expected behavior, even in cases where "Connection: keep-alive" is set, for the container to force it to "Connection: close"? I would think that if the response header is already set by the application, that the container should honor it (unless maxKeepAlive is exceeded, or persistent connections are disabled). I haven't seen anything in the HTTP 1.1 spec saying that a status of 400 requires that the connection be closed. The only case where a server is required to close a connection is when the request includes "Connection: close" but other than that, it appears to be optional (with the default being persistent connections). Am I missing something? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
