iis-arr | 易学教程

IIS URL Rewrite based on logged in user

阅读更多关于 IIS URL Rewrite based on logged in user

问题 I have a scenario whereby I want to route http requests from authenticated users to specific websites hidden behind a reverse proxy. The decision of which site to route too is based on the specific user. For example, user 'Mary' may be routed to site "b"; user 'John' may be routed to site "e". I am hosting the sites on IIS and am using ARR as my reverse proxy. I'm trying to figure out the best way to use URL Rewrite to make the routing decision. One idea I had was to build a custom URL

Adding a custom header to ARR requests

阅读更多关于 Adding a custom header to ARR requests

I'm running a service behind IIS using ARR as a reverse proxy. I know there are x-forwarded-for and x-arr-log-id headers that are passed along. However, what I would like is a private key passed in so that the backing application explicitly knows that the request is not local (even though the ARR server is). I've seen some posts on adding/replacing server variables, but this doesn't seem to come through via the request headers on the backing application. I'm guessing that there must be some web.config setting that will do this, but have had no luck finding it thus far. Example: X-PRIVATE-TOKEN

Adding a custom header to ARR requests

阅读更多关于 Adding a custom header to ARR requests

问题 I'm running a service behind IIS using ARR as a reverse proxy. I know there are x-forwarded-for and x-arr-log-id headers that are passed along. However, what I would like is a private key passed in so that the backing application explicitly knows that the request is not local (even though the ARR server is). I've seen some posts on adding/replacing server variables, but this doesn't seem to come through via the request headers on the backing application. I'm guessing that there must be some