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
As in #1827 discussed the remote IP from a client could be different the the remoteAddr Variable. Some Applications, nowadays, run behind a reverse proxy and send the real client IP in http headers like X-Forwarded-For or Forwarded HTTP Extension which should be parsed and set the remoteAddr, or another Variable, with that header value.
There are two to-do's from my point of view.
[ ] Implement Forwarded and/or X-Forwarded-For Parser in a fresh plugin
[ ] Create a example to show the usage of the plugin.
The text was updated successfully, but these errors were encountered:
No, as described in #1827 this should not live in the Fresh code base at all, neither directly in Fresh, nor as a plugin. Adding it to the Fresh repository would imply that we would keep it up to date and maintain it. We won't do that. It should either live in the project's code directly as a middleware or as a plugin in a separate repository. I'm happy to point to that from the docs once a repository for a plugin exists or something like that.
As in #1827 discussed the remote IP from a client could be different the the remoteAddr Variable. Some Applications, nowadays, run behind a reverse proxy and send the real client IP in http headers like X-Forwarded-For or Forwarded HTTP Extension which should be parsed and set the remoteAddr, or another Variable, with that header value.
There are two to-do's from my point of view.
[ ] Implement Forwarded and/or X-Forwarded-For Parser in a fresh plugin
[ ] Create a example to show the usage of the plugin.
The text was updated successfully, but these errors were encountered: