Fluid Topics additional header - Fluid Topics - Latest

How to Integrate Fluid Topics Via a Proxy Server

Category
Technical Notes
Audience
public
Version
Latest

A Fluid Topics portal is typically accessible via a domain name such as https://documentation-portal/ (e.g. https://docs.acme.com).

In the case where the default domain name does not align with a website's standardized URL, it is possible to configure a proxy server to use a specific path as the Fluid Topics root URL. Instead of relying on the Domain Name System (DNS), the Fluid Topics root URL becomes accessible via a sub-path (e.g. docs in the example below).

For example https://institutional-portal/docs (e.g. https://www.acme.com/docs).

However, because the HTTP headers do not inherently carry the path information, resolving the full base URL request is challenging.

To address this issue, the Fluid Topics server supports the following custom header:

  • FT-Forwarded-Path: this header carries the base URL path segment to the Fluid Topics server.

The diagram below illustrates how headers are forwarded to the Fluid Topics server.

Diagram illustrating the flow of an HTTPS request from a web interface to a server. On the left, a computer and a tablet display a documentation site with the URL 'https://www.dronelift.net/docs'. An arrow labeled 'https request' points to a 'Web Front' server box. Three arrows labeled 'X-Forwarded-Proto: https', 'X-Forwarded-Host: www.dronelift.net', and 'FT-Forwarded-Path: docs' point from the 'Web Front' to a 'Fluid Topics Server' on the right.