deiu / solidproxy Goto Github PK

The proxy currently supports only one user that it gets from env. It should also be able to support multiple users, like in the case where it serves requests from a Solid server with lots of vhosts (e.g. databox.me).

If a user requests a large amount of resources through the proxy, the server should only handle them in parallel if there is a cookie/session opened with the target server. This way, we avoid doing the WebID-TLS auth dance multiple times.

Right now the proxy is tested against HTTP GETs. Need more tests for other methods used by Solid, such as POST/PUT/HEAD/OPTIONS.

Do not attempt to retry fetching with credentials after an HTTP 401 if no user is provided to the fetcher.

Attempt to move away from using github.com/elazarl/goproxy. It should work with net/http.

Sending two requests per resource adds up. Let's keep a cache of the set of resources which have asked for credentials in the past. For requested resources, we'll check the cached set to inform whether we should try with or without credentials.

Add a Docker config file.

The proxy needs to pass along any headers it receives from the requesting client.

Add documentation explaining what the code does.

Handle the scenario where a server decides to revoke its cookie.

There are currently a few config variables that are defined with a global scope. They should be passed to the handler functions during init phase instead.

The current version does not maintain persistent (keepalive) connections when fetching data from other servers. It should reuse the same client object when requesting additional resources.