in reply to EOF problem with Dancer streaming proxy

I've patched Dancer locally to not add the Content-Length header for streamed resources that don't have a content length. If I remember correctly, Dancer forces some headers on every response even if they are not needed or even harmful.

I'm not sure what the proper response for streamed, non-delimited content types like text/event-stream should be but maybe someone can divine that from the standards...

Replies are listed 'Best First'.
Re^2: EOF problem with Dancer streaming proxy
by dsheroh (Monsignor) on Jan 12, 2017 at 14:50 UTC
    Strange. I am using Dancer 1.3202, the same as the version of the source you linked to, but wget doesn't show a Content-Length header as being present: 
    $ wget -S http://foo/bar.pdf
--2017-01-12 15:43:26--  http://foo/bar.pdf
Resolving foo
Connecting to foo:80... connected.
HTTP request sent, awaiting response... 
  HTTP/1.1 200 OK
  Date: Thu, 12 Jan 2017 14:43:26 GMT
  Server: Apache/2.4.10 (Debian)
  Content-Type: application/pdf
  Content-Disposition: inline; filename="bar.pdf"
  Keep-Alive: timeout=15, max=100
  Connection: Keep-Alive
  Transfer-Encoding: chunked
Length: unspecified [application/pdf]

    [download]
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom