Tornado ignores duplicate `Transfer-Encoding: chunked` headers, which leads the server to treat requests as having no message body. Consequently, the chunked body is parsed as a subsequent request. When deployed behind proxies that forward requests containing multiple `Transfer-Encoding: chunked` headers, this inconsistency allows for HTTP request smuggling. This can result in access control bypass, cache poisoning, or connection desynchronization.