GET Request using Host Header Value not IP Address

when HTTP_REQUEST {
     HTTP::header replace Host "myspserver1.mydomain.com"
}

Can you elaborate on how you set up your aams and any dns entries to make all this work. I am struggling to set up the same kind of thing. ==Lee

The beauty of the above iRule is that you may not have to modify AAM at all. By default SharePoint should set an AAM entry for the local machine's server name. Without making any modifications, client requests coming from the Internet that send a Host header that doesn't match this value will get redirected to this value (and subsequently break). So you could either modify AAM on each SharePoint server to match the external name of the application, or use an iRule on the F5 to change the Host header to what the SharePoint server expects.

OK, slight variation

I have my F5 pool set up - it points to my 2 wfes and appears healthy I am accessing the network via a VPN using the same F5 server that my pool is running on.

In DNS, I have my sharepoint host header(xxxportal) pointing to the F5 virtual IP for the sharepoint pool. xxx.xx.xx.110

New question, what do I have to put in my local host file. I can access the site if I use the IP of either sharepoint front end in my host file.

If I use the address of the virtual server, .110, it does not work.

What else might I need in my F5 configuration.

Thanks for listening and patience. ==Lee

I can access the site if I use the IP of either sharepoint front end in my host file.

Does this mean you're going around the F5? If so, whatever you have in SharePoint's AAM configuration is what you need in the Host header. The easiest thing would probably be to add the external name to AAM, but in lieu of that, the above iRule needs to replace the host header with a name that the SharePoint server likes. If you have multiple SharePoint servers with their own AAM settings, then you'd also need a way to switch these values in the iRule based on the load balanced server IP.

To be more specific, here is generally what I have done. SharePoint Web Application host header: xxxportal Web Application URL: http://xxxportal AAM: Public: http://xxxportal Internal http://xxxportal

DNS entry xxxportal.rest of fqdn pointing to xxx.xx.xx.110 (Virtual IP of the pool)

I know this is one of those foot bone connected to ankle bone, ankle bone connected to leg bone, leg bone ..... and I am just missing a piece or two.

I have not added any Alternate access mappings to this point. Should I have?

Thanks for listening. ==Lee

I am accessing this all through a VPN that uses an F5 webtop. That is why I put an entry into my local host file in the first place. The local entry is xxxportal and I have tried pointing it to .110 but that does not work.

Thanks for your patience and any help. ==Lee

The goal of all of this is to get a Host header to SharePoint that it will accept, per its AAM settings. If the browser makes a request to https://sp.example.com, that Host header will pass through the proxy/load balancer and arrive at the SharePoint server. If SharePoint doesn't have an AAM entry for https://sp.example.com in the zone that it thinks the traffic is coming from, then it will redirect the client to the URL that is in AAM. So considering the that SharePoint has an internal name, and you have an external name that you want to use to access SharePoint, you have basically two options:

1. Add the external URL to the Internet zone in AAM

    

2. Rewrite the Host header to the internal name as it passes through the proxy