The connection lines between Virtual Hosts, Mappings,and Back-end Groups define how HTTP requests are forwarded to the back-end applications.
Airlock Gateway always matches the most qualified entry path first. A back-end application should either use relative HTTP links in its HTML pages and HTTP headers, or both the entry and back-end path should be equal. If both is not the case, the content rewriting settings may be needed to make the application reverse proxy compatible (see HTTP/HTML rewriting).
- A mapping may be connected to one or more virtual hosts. If no virtual host is connected, a warning is displayed and the mapping will not be accessible after activation.
- A mapping may be connected to one or more back-end groups. Errors are displayed when a mapping is not connected to a back-end group or if one or more back-end groups are not configured correctly. See also Dynamic back-end group selection.
Due to the many-to-many relationships between the virtual hosts and mappings, only the connections of the selected element are shown. The selected element and its connected 'neighbors' are always shown at the top of the list. The remaining (not directly connected) elements are listed below (sorted alphabetically).