Forum Discussion
nash_65851
Apr 12, 2013Nimbostratus
Thanks for the responses guys.. I stand corrected, I did the foolish thing and assumed that it was sending the request with the IP address in the host header (I assumed this due to the fact that I configured the pools with an IP address - Stupid, I know)... I did a packet capture and indeed the request is sent with the what the client requests in the browser.
This was still causing the issue with the AAM in sharepoint though as the client comes to the big ip on an external host name, but the resource is an internal host name. The external host name is not set up in the AAM.
@Kevin - Thanks for the snippet of code, that sorted the issue out for me and all is well.
Thanks for the schooling, I have learnt my lesson for today, I can now go home!