Aaron Lehmann e7435725af Don't panic when a http.ResponseWriter does not implement CloseNotifier ... Instead, provide a variant of instrumentedResponseWriter that does not implement CloseNotifier, and use that when necessary. In copyFullPayload, log instead of panicing when we encounter something that doesn't implement CloseNotifier. This is more complicated than I'd like, but it's necessary because instrumentedResponseWriter must not embed CloseNotifier unless there's really a CloseNotifier to embed. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>		2015-08-06 15:50:54 -07:00
..
api	Add blob delete entry to api description and regenerate api.md	2015-08-03 11:59:19 -07:00
auth	auth.AccessController interface now uses distribution/context	2015-07-23 19:48:47 -07:00
client	Add pull through cache functionality to the Registry which can be configured	2015-08-04 16:09:55 -07:00
handlers	Don't panic when a http.ResponseWriter does not implement CloseNotifier	2015-08-06 15:50:54 -07:00
listener	[Server] Listen and serve on a unix socket	2015-05-11 16:00:14 +03:00
middleware	Add pull through cache functionality to the Registry which can be configured	2015-08-04 16:09:55 -07:00
proxy	Add pull through cache functionality to the Registry which can be configured	2015-08-04 16:09:55 -07:00
storage	Merge pull request #779 from RichardScothern/pull-through-cache	2015-08-04 17:04:56 -07:00
doc.go	Integrate layer info cache with registry and storage	2015-04-02 20:15:16 -07:00