Caddy 0.9.3 breaks chunked connections

Help
1

I was using Caddy 0.9.0 to proxy a server that returns a chunked HTTP response to simulate a push connection. This worked fine (clients would connect and receive the streaming data properly) until I upgraded to 0.9.3. With that version, Caddy waits for the response to terminate (and thus waits forever), with no way for me to actually start receiving data live.

Is there a new parameter that I can use to get the old behaviour back, or is this a bug?

2

There’s a lot of changes between those two versions. What’s your setup?

If you think it’s a bug, file an issue and follow the template thoroughly because if we can’t see the same behavior you’re describing it can’t be fixed. :-/ Thanks!

3

This is my config:

log /var/log/caddy/log.log
header / Strict-Transport-Security "max-age=31536000; includeSubdomains";
proxy / http://localhost:1234/ {
    transparent
}

It’s proxying a Gweet instance:

You can just launch Gweet and Caddy with that config, connect with:

curl --raw "http://localhost/stream/test/?streaming=1"

and create a message with:

curl -X POST "http://localhost/stream/test/?foo=bar"

Normally, you should see the message appear in the stream, but after 0.9.0 it doesn’t any more.

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.