« Previous Next »

Thread: httpPort and httpsPort in ARR

Last post 12-31-2008 6:53 PM by bb1769. 2 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (3 items)

Sort Posts:

  • 12-30-2008, 4:47 PM

    • bb1769
    • Not Ranked
    • Joined on 06-03-2003, 12:27 PM
    • Posts 2

    httpPort and httpsPort in ARR

    I need to reverse proxy to a server on non-default http/https ports (8080/8443). I used the appcmd method mentioned in the comments in this post to add the setting in IIS7:
    forums.iis.net/t/1153071.aspx

    When I list the contents of the webFarms (appcmd list config /section:webFarms), it shows the httpPort and httpsPort attributes:

    <webFarms>
      <webFarm name="myReverseProxy" enabled="true">
        <applicationRequestRouting>
          <protocol />
          <healthCheck />
          <affinity>
          </affinity>
          <loadBalancing />
        </applicationRequestRouting>
        <server address="myServer" enabled="true">
          <applicationRequestRouting httpPort="8080" httpsPort="8443" />
        </server>
      </webFarm>
    </webFarms>

    But when I request a resource through the server farm, it sends the request to the reverse proxy machine on port 80 (verified using Wireshark). Is this the correct attribute, or does something else need to be added/done? Thanks for any help.

  • 12-30-2008, 5:11 PM In reply to

    • anilr
    • Top 10 Contributor
    • Joined on 05-23-2006, 10:13 PM
    • Redmond, WA
    • Posts 2,343

    Re: httpPort and httpsPort in ARR

    And what does your url-rewrite looks look like (globalRules and/or rules sections)?  Also, if all you have is one content server, using a web-farm is a bit of an overkill, you can just specify the server-name in the url-rewrite rule in that case along with the port number.

    Anil Ruia
    Senior Software Design Engineer
    IIS Core Server
  • 12-31-2008, 6:53 PM In reply to

    • bb1769
    • Not Ranked
    • Joined on 06-03-2003, 12:27 PM
    • Posts 2

    Re: httpPort and httpsPort in ARR

    Thanks for the response. It started working - not sure why, but it's now sending to the correct port.

    As for whether to just use URL Rewrite, I'd read that ARR would be needed to do a reverse proxy with URL Rewrite. In my case, if I bypass ARR and just do a rewrite rule to the back end server, the Host header variable gets changed to the back-end server. This causes problems because the Web application on the back-end server uses the Host header in some URLs within the page it returns. The URLs thereby point to the back-end server, which the client cannot reach directly. If I send requests through ARR it doesn't modify the Host header.

Page 1 of 1 (3 items)
Microsoft Communities