HTTPS and URL Redirection

The Omniscope web server includes built-in support for HTTPS and flexible URL redirection. These features are useful for maintaining consistent access to dashboards, managing domain changes, and enhancing security.

This article explains how to configure redirection rules and HTTPS settings using Omniscope’s internal web server.

Find the settings in Admin -> Network

? Redirection Types in Omniscope

Omniscope applies redirection rules in the following order:

1. URL Redirection

This allows incoming requests to be redirected to:

• A different host (domain)

• A different context path (folder or dashboard)

Use cases:

• URL shortening

• Preventing broken links

• Serving the same dashboard from multiple domains

• Guiding users from outdated or bookmarked URLs to current ones

? Redirection Examples

✅ Host Redirection

Redirects clients from one domain to another.
Example: Redirect users from http://alpha.omniscope.me to https://omniscope.me.

Result:

http://alpha.omniscope.me/folder/file.iok → https://omniscope.me/folder/file.iok

✅ Context Redirection

Redirects a specific path (context) to another path on the same domain.
Example:
Redirect from /dashboard to a specific dashboard file.

Result:

http://server.domain/dashboard → http://server.domain/MyDefinitelyBeautifulDashboard.iok

✅ Host + Context Redirection

Redirect from both a different host and a different path.
Example:
Redirect from http://alpha.omniscope.me/demo to https://demoserver/MyBeautifulDashboard.iok.

Result:

http://alpha.omniscope.me/demo → https://demoserver/MyBeautifulDashboard.iok

?️ Configuration Notes

• Redirect from:
  Define the path to redirect from (e.g. /, /dashboard, /demo).

• Redirect to:
  Provide the full target path or URL (e.g. /MyDashboard.iok or https://otherhost.com/path/file.iok).

• Virtual Hosts:
  List the domain(s) the rule applies to. Leave empty to apply the rule to all incoming hosts.

• Blank “Redirect from” Field:
  If you leave the “Redirect from” field blank, the redirection applies to all incoming requests. In that case, the “Redirect to” field should contain a fully qualified URL, including protocol and domain.

⚠️ Be careful to avoid redirect loops, especially when redirecting all incoming requests. Ensure that your target URL does not trigger the same redirect again.

? Enforcing HTTPS

Omniscope can redirect all HTTP traffic to HTTPS when HTTPS is enabled.

To enable:

• Turn on the Redirect HTTP to HTTPS option.

• Ensure a valid SSL certificate is configured.

Result:

http://yourdomain.com → https://yourdomain.com

This helps enforce secure communication for all users accessing your dashboards.

✅ Best Practices

• Test redirection settings carefully to avoid loops or misroutes.

• Use host+context redirection for complex domain restructuring.

• Leave Virtual Hosts blank only when applying redirection globally.

• Always use HTTPS for login and dashboard access where possible.

• Configure fallback authentication (e.g. local user/pass) in case SSO fails.

For further assistance or configuration support, contact your Omniscope administrator or support team.