IIS REMOTE_ADDR

Hey,

 

The configuration involving the priority group for direct access to the

 

HTTP servers via the LTM in case of ASM failover was suggested and

 

configured by an F5 ASM consultant as best practice. We do indeed have a

 

failover pair of ASMs but the consultant deemed this configuration as

 

the best way to ensure 0% downtime for our properties.

 

Have you heard of anyone loading an ISAPI filter on the IIS server

 

directly to make this change? I saw a posting on devcentral in which the

 

developer "faked" IIS into adding the Xforward information into the IIS

 

logs instead of the actual client ip. Perhaps the same "fake" could be

 

done for standard use of REMOTE_ADDR. Thoughts?

 

Thanks,