Stephen J Day 4158c70f58 Avoid panic on write after close in http ...

By adding a (*WriteFlusher).Close, we limit the Write calls to possibly
deallocated http response buffers to the lifetime of an http request.
Typically, this is seen as a very confusing panic, the cause is usually a
situation where an http.ResponseWriter is held after request completion. We
avoid the panic by disallowing further writes to the response writer after the
request is completed.

Signed-off-by: Stephen J Day <stephen.day@docker.com>
(cherry picked from commit ec2289b2d9ac79fd5e0f69f56f023dfe8ee78bf8)

2015-11-09 18:36:27 -05:00

..

auth.go

refactor away direct references to daemon member

2015-10-09 14:40:03 -07:00

container.go

Avoid panic on write after close in http

2015-11-09 18:36:27 -05:00

copy.go

Separate API router from server.

2015-09-29 19:43:03 -04:00

exec.go

Cleanup some issues with exec

2015-10-06 15:22:20 -04:00

image.go

Avoid panic on write after close in http

2015-11-09 18:36:27 -05:00

info.go

Avoid panic on write after close in http

2015-11-09 18:36:27 -05:00

inspect.go

add size to inspect

2015-10-10 20:44:29 +08:00

local.go

rename POST /volumes to POST /volumes/create to be consistent with the other POST /.../create endpoints

2015-10-22 15:07:06 -04:00

volume.go

Separate API router from server.

2015-09-29 19:43:03 -04:00