You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is for convenience, so that we don't have to install additional reverse proxies like Nginx, HAProxy etc.
We usually use those for (1) reverse proxy and (2) static file serving. Xitrum is already good at (2), adding (1) will make Xitrum more complete.
Example:
Site X is written with Xitrum. It also needs to integrate Discourse. With this reverse proxy feature, we can mount Discourse at /forum of site X.
For now, we don't support request and response interception.
In the future, we can:
Allow code to intercept requests and responses to modify (headers etc.) or extract info.
For performance, we avoid parsing as much as possible. Probably we only need to (1) look at the first request line to know the URL and (2) inject proxy info headers to the request. We don't modify responses, just send them as-is.
Why this is a good feature to have?
Example:
Site X is written with Xitrum. It also needs to integrate Discourse. With this reverse proxy feature, we can mount Discourse at
/forum
of site X.For now, we don't support request and response interception.
In the future, we can:
respondProxy
for actions.How to implement?
Headers to set:
The text was updated successfully, but these errors were encountered: