search for: impoundment

Displaying 2 results from an estimated 2 matches for "impoundment".

2018 Oct 29
2
Should Icecast send the "Connection: close" header?
...would be better for Icecast to send the "Connection: close" header. One client-side workaround I can think of is to disable connection re-use for any chunked transfers, but that seems maybe overly-conservative. Here's the transaction I'm seeing: $ curl -v doppler.media.mit.edu/impoundment.ogg * Trying 18.85.59.166... * TCP_NODELAY set * Connected to doppler.media.mit.edu (18.85.59.166) port 80 (#0) > GET /impoundment.ogg HTTP/1.1 > Host: doppler.media.mit.edu > User-Agent: curl/7.58.0 > Accept: */* > < HTTP/1.1 200 OK < Date: Mon, 29 Oct 2018 15:58:27 GMT &lt...
2018 Oct 29
0
Should Icecast send the "Connection: close" header?
...Connection: close" header. see above. > One client-side workaround I can think of is to disable connection > re-use for any chunked transfers, but that seems maybe > overly-conservative. > > Here's the transaction I'm seeing: > > $ curl -v doppler.media.mit.edu/impoundment.ogg > * Trying 18.85.59.166... > * TCP_NODELAY set > * Connected to doppler.media.mit.edu (18.85.59.166) port 80 (#0) > > GET /impoundment.ogg HTTP/1.1 > > Host: doppler.media.mit.edu > > User-Agent: curl/7.58.0 > > Accept: */* > > > < HTTP/1.1 200 OK...