You should be able to use sendError(-1) which will immediately abort the HttpChannel and close the connection/stream.
see https://www.eclipse.org/jetty/javadoc/jetty-10/org/eclipse/jetty/server/Response.html#sendError(int,java.lang.String) On Wed, Oct 12, 2022 at 12:13 PM Dung Nguyen <chong.xi...@gmail.com> wrote: > Connection : close doesn't solve the problem. > > Vào Th 4, 12 thg 10, 2022 vào lúc 05:00 Greg Wilkins <gr...@webtide.com> > đã viết: > >> >> >> On Wed, 12 Oct 2022 at 05:13, Simone Bordet <sbor...@webtide.com> wrote: >> >>> For other protocols such as HTTP/2 or HTTP/3, adding the `Connection: >>> close` header will have no effect. >>> >> >> Thinking out loud here... >> >> Whilst there is no requirement to close a HTTP/2 or HTTP/3 connection >> when a "Connection: close" header is seen, I wonder if we could perhaps use >> that as a hint to shutdown the connection (well reduce the number of >> streams to 0 and let other streams complete and then close). This would >> be useful in graceful shutdown scenarios... but perhaps the header is the >> wrong way to signal that? >> >> -- >> Greg Wilkins <gr...@webtide.com> CTO http://webtide.com >> _______________________________________________ >> jetty-users mailing list >> jetty-users@eclipse.org >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/jetty-users >> > _______________________________________________ > jetty-users mailing list > jetty-users@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list jetty-users@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
