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_test.go	Fix for api_test.go	2015-07-28 10:59:11 -07:00
app.go	Add pull through cache functionality to the Registry which can be configured	2015-08-04 16:09:55 -07:00
app_test.go	Add pull through cache functionality to the Registry which can be configured	2015-08-04 16:09:55 -07:00
basicauth.go	Move registry package into handler package	2015-02-10 17:25:40 -08:00
basicauth_prego14.go	Move registry package into handler package	2015-02-10 17:25:40 -08:00
blob.go	Manifest and layer soft deletion.	2015-07-24 09:57:20 -07:00
blobupload.go	Factor CloseNotifier use into a new function	2015-07-31 17:30:26 -07:00
catalog.go	Create Repositories method	2015-07-21 21:45:14 -07:00
context.go	Create Repositories method	2015-07-21 21:45:14 -07:00
helpers.go	Don't panic when a http.ResponseWriter does not implement CloseNotifier	2015-08-06 15:50:54 -07:00
hmac.go	Refactor Blob Service API	2015-05-15 17:05:18 -07:00
hmac_test.go	Refactor Blob Service API	2015-05-15 17:05:18 -07:00
hooks.go	Feature: Web Panic Reporting via hooks	2015-05-31 14:21:22 +00:00
images.go	Factor CloseNotifier use into a new function	2015-07-31 17:30:26 -07:00
mail.go	Feature: Web Panic Reporting via hooks	2015-05-31 14:21:22 +00:00
tags.go	Allow Manifest Service to be configured with function arguments	2015-07-15 12:25:16 -07:00