tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 53169] New: [patch] don't do chunking with Connection: close
Date Tue, 01 May 2012 09:35:06 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=53169

          Priority: P2
            Bug ID: 53169
          Assignee: dev@tomcat.apache.org
           Summary: [patch] don't do chunking with Connection: close
          Severity: minor
    Classification: Unclassified
                OS: All
          Reporter: kustos@gmx.net
          Hardware: All
            Status: NEW
           Version: trunk
         Component: Catalina
           Product: Tomcat 7

Created attachment 28702
  --> https://issues.apache.org/bugzilla/attachment.cgi?id=28702&action=edit
patch against trunk

The attached patch disables chunking on if there is a Connection: close header,
we're on HTTP 1.1 and there's no Content-Length header.

This helps to implement Server-Sent Events [1]. Server-Sent Event are
conceptually similar to the forever streaming iframe in the sense that there's
an "infinite" response from the server that always gets updated. But they're
easier to use and with less issues. They are also easier to use than WebSockets
if you don't need a back channel.

The specification reccoments to disable chunking. Jetty implements the same
behavior, when there's a Connection: close header it doesn't do chunking.

The following discussion [2] leads me to believe that patches would be welcome.
The patch comes with unit tests that verify that there is still chunking
happending when there is no Connection: close header.

 [1] http://dev.w3.org/html5/eventsource/#notes
 [2]
http://tomcat.10.n6.nabble.com/How-to-disable-chunked-encoding-for-the-Http11NioProtocol-connector-td2038448.html

-- 
You are receiving this mail because:
You are the assignee for the bug.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message