Summary: | tomcat-embed:chunked responses with header 'connetion:close' are damaged | ||
---|---|---|---|
Product: | Tomcat 9 | Reporter: | taojiaen <taojiaen> |
Component: | Servlet | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 9.0.x | ||
Target Milestone: | ----- | ||
Hardware: | All | ||
OS: | All |
Description
taojiaen
2020-03-22 16:06:35 UTC
If the application takes responsibility for setting the chunked encoding header it also has to take responsibility sending for a correctly encoded body. Generally, it is much simpler to let the container handle chunked encoding. (In reply to Mark Thomas from comment #1) > If the application takes responsibility for setting the chunked encoding > header it also has to take responsibility sending for a correctly encoded > body. > > Generally, it is much simpler to let the container handle chunked encoding. Even If I change the body into a simple character or other string, it also damaged.How can I solve this problem ? I just send a simple character is it not a correctly body?and It worked well when I use jetty or undertow, when I remove the header "connetion:close", it also worked well. Have I do some illegal operation? (In reply to Mark Thomas from comment #1) > If the application takes responsibility for setting the chunked encoding > header it also has to take responsibility sending for a correctly encoded > body. > > Generally, it is much simpler to let the container handle chunked encoding. thx for reply a really want to know what happend, I have worked it on for weeks and have no idea about it. the related bug is reported on github https://github.com/spring-cloud/spring-cloud-gateway/issues/1600#event-3129620407 https://github.com/spring-projects/spring-framework/issues/24699#issuecomment-600742824 Bugzilla is not a support forum. If you want to ask questions, use the Tomcat users mailing list. |