Redirect Options

Learn how to configure redirect settings to control how requests are forwarded from the source URL to the target URL.

Redirect settings allow you to fine-tune how the Medianova Panel processes incoming requests before forwarding them to the target URL. You can configure path handling, query parameters, and HTTPS behavior to ensure redirects work exactly as needed.

Path Forwarding

Path forwarding determines how the path portion of the source URL (the part after the domain) is handled during the redirect. Medianova supports three modes:

• All: Forwards the entire path from the original request to the target.

• None: Ignores the original path and always redirects to the base or fixed target URL.

• Capture: Forwards only the variable part that matches a wildcard or pattern, excluding the fixed part.

Mode	Description	Example
All	Forwards the entire path.	oldsite.com/docs/page1 → newsite.com/docs/page1
None	Ignores the original path.	oldsite.com/docs/page1 → newsite.com
Capture	Forwards only the wildcard/variable part.	oldsite.com/docs/* → newsite.com/page1

Ensure the source pattern matches correctly; otherwise the redirect may not trigger. Using wildcards (e.g., *) or partial paths helps capture a wider range of requests.

Query Forwarding

Controls whether query parameters (the part of a URL after ?) are passed along to the target URL.

• Enabled: Keeps the original query string. This is useful if the destination page needs the same parameters.

• Disabled: Removes the query string. This helps simplify URLs when the parameters are not required.

Enable this option only if your target can handle the same parameters. Otherwise, it’s better to disable to avoid unnecessary complexity.

Mode	Description	Example
Enabled	Query string is forwarded.	example.com?page=1 → destination.com?page=1
Disabled	Query string is dropped.	example.com?page=1 → destination.com

HTTPS Options

Redirect behavior over HTTPS can be customized with two options: Enable HTTPS and Force HTTPS.

• Use Enable HTTPS to support secure requests with an automatically managed SSL/TLS certificate.

• Use Force HTTPS to ensure all traffic is encrypted, even if users try to connect over plain HTTP.

Option	Description	Example
Enable HTTPS	Accepts secure requests over HTTPS. SSL/TLS certificates are provisioned automatically.	https://oldsite.com → https://newsite.com
Force HTTPS	Redirects all HTTP requests to HTTPS before forwarding. Must be used with Enable HTTPS.	http://oldsite.com → https://oldsite.com → https://newsite.com