proxying the app? nginx or other

[ThomasCartier]

Hi,
Functions can have a dev defined address/endpoint.
Now if I want the app to listen to 0.0.0.0:7890 and have a proxy on port 12000, the wasm calls will land on port 7890 and not 12000.

The goal is to have a proxy dealing with tls and auth, while having the app receive the modified request from the reverse proxy( nginx, pingora..)

What would be the best way to express it? Should we have a further option: proxy_addr for example?

Thanks guys for the great work do far

[ThomasCartier]

The issue is related to the calls from the interface in a fullstack app that will directly point to the endpoint, but instead, they should point to another address (the proxy) while the server listens at its endpoint. This way, the proxy knows where to forward the request. In a non hacky way. I really think a new attribute should be created for this purpose.

Do you think it's possible ?