David Wragg b56ff7678c Make code coverage work through the proxy ...

Previously, the proxy would run the weave script in ways that did
not run the weaver executable.  Now they can.  This is a problem because
of the contortions involved in using golang's code coverage support
in the integration tests, which require the weaver command line args to
be slightly mangled.

2015-10-12 21:27:11 +01:00

..

chunked_test.go

review feedback

2015-08-10 11:02:51 +01:00

chunked.go

review feedback

2015-08-10 11:02:51 +01:00

common.go

Make code coverage work through the proxy

2015-10-12 21:27:11 +01:00

create_container_interceptor.go

review feedback

2015-10-12 15:53:07 +01:00

create_exec_interceptor.go

[proxy] all request modification is done through map[string]interface{}

2015-10-12 15:53:07 +01:00

inspect_container_interceptor.go

[proxy] all request modification is done through map[string]interface{}

2015-10-12 15:53:07 +01:00

inspect_exec_interceptor.go

[proxy] all request modification is done through map[string]interface{}

2015-10-12 15:53:07 +01:00

interceptor.go

proxy interceptors implicitly modify arguments, instead of returning them

2015-05-19 10:34:46 +01:00

json_test.go

review feedback

2015-10-12 15:53:07 +01:00

json.go

review feedback

2015-10-12 15:53:07 +01:00

proxy_intercept.go

Proxy chunking should handle arbitrarily large chunks

2015-08-04 17:47:51 +01:00

proxy.go

Make code coverage work through the proxy

2015-10-12 21:27:11 +01:00

start_container_interceptor.go

[proxy] all request modification is done through map[string]interface{}

2015-10-12 15:53:07 +01:00

tls.go

[proxy] Add tls support

2015-06-05 13:23:14 +01:00