IIS 7.5 Server behind an F5 Reverse Proxy

[Cantor, Scott]

On 8/20/14, 1:00 PM, "Meiselman, Ellen" <emeiselm at med.umich.edu> wrote:
>
>They can't, unfortunately. The root of the domain proxyserver.com is
>being used for the LMS application. The /content/ subdirectory is being
>used for our SCORM content which has to use the same domain, protocol,
>port, etc. so that javascript can communicate across frames.

The first mistake was really using frames then, they should be banned at
this point.

>So that means I still probably have a path problem with my setting for
>the metadata handler.

No, it means your system doesn't know what it's named and how it's being
accessed. When you virtualize a system, the web server needs extensive
features to support that. IIS has none of them, so at a basic level it
does not support load balancers. If you can't tell a web server that its
logical settings are different from its physical settings, then you can't
virtualize it unless all the applications running on it are themselves
broken and ignore the web server's own reporting of the values to
applications.

The SP compensates for that imperfectly through the Site mappings in its
own configuration, and you haven't set those mappings up correctly to
report the virtualized scheme, port, or hostname, or all three.

The metadata handler is irrelevant anyway, it's for providing example
metadata, not for production use. None of your handlers are going to work,
and the assertion consumer service not working means the SP doesn't work
period.

-- Scott