While the client has a generic plugin mechanism allowing any scheme (https://, root://, ...), the proxy server enumerates the permitted schemes one-by-one.
I'm tinkering with a s3:// plugin for the client which would allow us to unify our HTTP and S3 support into one library (instead of nearly-identical code, once for the server, once for the client). Adding a small patch that exposes s3:// as a supported protocol in the proxy.
While the client has a generic plugin mechanism allowing any scheme (
https://,root://, ...), the proxy server enumerates the permitted schemes one-by-one.I'm tinkering with a
s3://plugin for the client which would allow us to unify our HTTP and S3 support into one library (instead of nearly-identical code, once for the server, once for the client). Adding a small patch that exposess3://as a supported protocol in the proxy.