Search results matching tag 'application Request Routing reverse proxy'

Re: Did ARR v2 RC break my URL Rewrite Rule custom serverVariables?

wonyoo — Mon, 28 Sep 2009 15:11:32 GMT

ARRv2 RC is shipped with URL rewrite v2 RC1. As a part of security feature, in URL rewrite v2 RC1, you have to explicitly manage the allow and deny list. The documentation on this is at http://learn.iis.net/page.aspx/686/setting-http-request-headers-and-iis-server-variables/

Re: Simple redirect question

wonyoo — Sat, 25 Jul 2009 01:16:47 GMT

Depending on the FREB rule, you may not get any log. Are you collecting logs for response 200-999? The term "failed request" may seem confusing. The request does not have to fail, per se - it generates the traces based on the rule/criteria. So if you configure it to collect anything between 200-999, you should get the log. Based on the log, we can figure out what's going on with the URL rewrite rules.

Re: Simple redirect question

wonyoo — Thu, 23 Jul 2009 15:00:25 GMT

Dany

Yes, try that out and let me know if it works. Sounds like you probably have v1. What that means is when you click on the server node of the tree view in the navigation pane, you will see an "Application Request Routing" icon. Double click on that and on the top of the page, there will be a check-box for enabling (what we call, "sever level") proxy. You will want to do that.

As for rewrite vs. redirect - if you want to proxy the request, then you want rewrite (ie. the URL on the browse remains that of proxy). If you want to send 302 back to your client, then you want redirect. The difference, of course, is that in proxy case, your client thinks that they are connecting to the proxy. In redirect, the client is redirected (ie. the URL on the browser will change). Sounds like you want rewrite.

ARR + Forms Authentication

jortizv — Wed, 22 Jul 2009 15:05:27 GMT

Is there an easy way to configure Forms Authentication to be passed to the farm servers, the idea is to have the authentication happen at one server and another server will be access with those credentials, our application uses forms authentication, and when we hit another server directly on the farm by passes the form authentication, can anyone guide me on the most effective way to do this..

Any help would be appreciated.. thank you

Re: how to implmenent such URL rewrite rule in ARR?

wonyoo — Mon, 20 Jul 2009 16:40:21 GMT

George

Yes, the URL rewrite rules can be set at the site level, but ARR is scoped to the server. Note that when you click on the server, there are both URL rewrite icon as well as the ARR icon (but you won't see ARR icon at the site level).

Typically, for the ARR scenarios, we write the URL rewrite rules at the server level as well (the difference is that the rules are written to "globalRules" and they are applies to all sites.)

Regardless of whether you are writing the rules at the server level or at the site level, ARR's scope is the server, but for what you are doing, it may not matter, esp. if you only have one default website.

Re: how to implmenent such URL rewrite rule in ARR?

wonyoo — Sun, 19 Jul 2009 09:33:51 GMT

No, you don't need to move it. ARR is a "server" level feature, meaning it is available for all sites to use. Therefore, if you already have a site running on port 80, you will want to add an additional rule in URL rewrite conditions (using SERVER_PORT) so that the URL rewrite rule is apply only for the site that you want to use to proxy request to http://localhost:8081.

(ie. if you want to receive origin request on 8080 and route it to 8081, make sure that you apply the URL rewrite rule for the proxy only for 8080 using SERVER_PORT in the URL rewrite condition)

REMOTE_ADDR IP restriction and DFS

nelson_cerqueira — Wed, 15 Jul 2009 09:06:42 GMT

We install Microsoft Application Request Routing on a server and we are using it as a reverse proxy server.

All the url rewrite rules work, if we update the rule set with new rules everything still works but if we introduce or modify any rule that contains any IP condition and use REMOTE_ADDR as a variable the web server breaks and stop serving.

ie: <add input="{REMOTE_ADDR}" pattern="^(10.0.0.1|127.0.0.1)" />

We can only resume serving when we restart the web server.

This is very problematic as we use this reverse proxy as a production server and we cant be starting it whenever we want.

Can someone have any ideas for solving this? Many thanks.

Re: Need Help for setup rules

wonyoo — Thu, 25 Jun 2009 20:21:36 GMT

Could you provide more info on where you are getting the /directory2/ path? Is that embedded in the entity body of the response? I am little bit puzzled as to where you might be getting that info. Also, could you provide the URL rewrite rules and the scenarios that you are trying to enable.

Re: IIS7 as a Reverse Proxy

wonyoo — Tue, 31 Mar 2009 17:35:41 GMT

For a very simple reverse proxy, all you have to do is:

1. Select the server node on inetmgr.

2. Double click on Application Request Routing icon.

3. Select/check "Enable proxy".

4. Select/check "Use URL Rewrite to inspect incoming requests.

5. Enter the server of where you want to route the request to in "Reverse proxy" - ie. (myserver.contoso.com).

In above example, all requests that are received by ARR will be routed to myserver.contoso.com.