Project

General

Profile

Actions
Copy link

Feature #2309

closed

not chunked fastcgi

Added by tdeseyn about 13 years ago. Updated over 9 years ago.

Status:
Invalid
Priority:
Normal
Category:
-
Target version:
-
ASK QUESTIONS IN Forums:

Description

I would like to send Server-Sent-Events, and the standard suggests it is preferable to disable chunking.
In the Notes section of http://dev.w3.org/html5/eventsource/
"Authors are also cautioned that HTTP chunking can have unexpected negative effects on the reliability of this protocol. Where possible, chunking should be disabled for serving event streams unless the rate of messages is high enough for this not to matter."

I am using:
lighttpd/1.4.26 (ssl) - a light and fast webserver
Build-Date: Jul 18 2010 01:15:37

Thanks,
Wkr,

Tom

Files

prevent-chunked-transfer-encoding-for-server-sent-events.patch (3.22 KB) prevent-chunked-transfer-encoding-for-server-sent-events.patch chris.kilgour, 2014-10-28 22:18
Actions
Copy link
 #1

Updated by stbuehler about 13 years ago

  • Status changed from New to Invalid

if the client isn't capable of reading chunked encoding, it should use HTTP/1.0 instead of 1.1.
i see no reason to change anything on our side.

Actions
Copy link
 #2

Updated by chris.kilgour over 9 years ago

The cited recommendation has nothing to do with HTTP protocol level, but rather a recommendation from W3C for server-sent events.

The attached patch defaults fastCGI applications responding with "Content-Type: text/event-stream" to disable chunked responses unless the "Transfer-Encoding: chunked" header is also present in the response.

Actions
Copy link

Also available in: Atom