parrhesia-base / poem-proxy Goto Github PK

So far the proxy is configured by just passing in a string data source that contains the proxied server address. I want to update this to an actual configuration struct that is passed into the endpoint and contains information about protocol vs secure protocol, and just overall customizing more details about how the proxying is handled.

Allow the proxy to properly pass through DELETE requests

To ensure that this proxy follows standard best-practices, it is important to have the code reviewed by someone who isn't tied into this project, and who has experience with proxies.

Allow the proxy to properly pass through PUT requests

Come up with a simple templating system that can change various elements of the request headers/body based on a special syntax.

For example, we configure the proxy to change "${thing}" to "thung", and if ${thing} is contained in the request, it will be changed to "thung" before it reaches the server.

Come up with a simple templating system that can change various elements of the request headers/body based on a special syntax.

For example, we configure the proxy to change "${thing}" to "thung", and if ${thing} is contained in the server response, it will be changed to "thung" before it is sent along to the client.

Right now the proxy just forwards all client messages to the server. Then it does the same for the response to the client. I am not sure if this is all that a proxy requires, or if I need to add special proxy headers or copy another source of information that might be important.

This task is to investigate what proxy requirements there might be.

These tests should help ensure that the package continues to work even after being finished and no longer actively maintained.

Allow the proxy to properly pass through PATCH requests

Allow templating to be performed over the websocket connections.

Right now the proxy just copies all client headers and the body and then sends it to the server. Then it does the same for the response to the client. I am not sure if this is all that a proxy requires, or if I need to add special proxy headers or copy another source of information that might be important.

This task is to investigate what proxy requirements there might be.

This documentation should properly explain all components of this library as well as how to use them. Use docs.rs