Reverse proxies are used to make certain services available with an URL where they have not be available before. They are used to add functionality, e.g. authorization and authentication or to add caching. In the best case, an administrator should be able to swap a reverse proxy with another reverse proxy without the users notifying it. Reverse proxies should be transparent to the user, i.e. in the best case an user cannot tell if he is connected to a proxy or to the real service. If the access was granted, we therefore connect to the service using the same HTTP method and passing all request headers and body from the user. Since authorization was already done by the proxy, we remove the authorization header and as the proxy should use few memory ressources we do not support the HTTP ‘keep-alive’ option, i.e.. we close the connection after every request. To establish secure connections between the service and proxy we support two options: Bearer Tokens and TLS client certificates. The bearer token is used in the authorization header and the TLS client certificate is used during opening the TCP connection to the service.