locked
Web Application Proxy and X-MS-PROXY header RRS feed

  • Question

  • When used as an ADFS proxy the WAP server issues a HTTP header X-MS-PROXY - allowing the ADFS server to determine that the request is external.

    However, this is apparently not the case when the WAP is used as a pass-through proxy for other applications.

    Does anybody how a web application can determine whether it is called through a WAP passthrough proxy or direct?

    Thursday, February 23, 2017 10:35 AM

Answers

  • Would the IP source of the IP datagram show the IP address of the WAP server?

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Thursday, February 23, 2017 5:46 PM

All replies

  • Would the IP source of the IP datagram show the IP address of the WAP server?

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Thursday, February 23, 2017 5:46 PM
  • I am replacing a TMG with WAP.

    TMG always issues a HTTP header header HTTP_REVERSE_VIA

    Similarly WAP issues a HTTP header X-MS-PROXY - but beware, only for ADFS preauthenticated publications

    To identify a WAP published connection you need to check if REMOTE_ADDR is the WAP server

    Friday, February 24, 2017 10:08 AM