Rewrite Origin URLs

Learn how to manage Rewrite Origin URLs to modify how request paths are sent to your origin.

Rewrite Origin URLs enables you to transform incoming paths before they are forwarded to origin servers. You can configure Match Mode, Origin URI, Target URI, and Priority to adjust how paths are rewritten for directory changes, API restructuring, or backend routing needs.

You can manage Rewrite Origin URLs using the Medianova Control Panel or API.

In the Medianova Control Panel, go to CDN Resources, select your resource, and navigate to Origin Settings

Manage Rewrite Origin URLs

Follow the steps below to add and manage Rewrite Origin URLs for your CDN Resource.

1

Add a Rewrite Origin URL

Select Add to create a new Rewrite Origin URL.

The Add Rewrite Origin URL popup appears.

2

Configure Parameters

Fill in the required fields in the popup:

  • Match Mode — Choose how the incoming path is matched. Options include:

    • All files

    • Path

    • Full Path

    • Wildcard

  • Origin URI — Enter the incoming request path to match.

  • Target URI — Enter the new path that requests will be rewritten to.

  • Priority — Lower values are evaluated first when multiple Rewrite Origin URLs exist.

3

Save the Configuration

Select Add, then click Submit. Your Rewrite Origin URL is added to the list.

Match Mode Behavior

  • All files: Applies to every incoming request.

  • Path: Matches only the path portion of the request URI.

  • Full Path: Matches the exact full URL path.

  • Wildcard: Enables dynamic pattern matching using wildcard symbols.

Troubleshooting

Issue: Rewrite Origin URL does not apply. Cause: Incorrect Match Mode or Origin URI format. Fix: Verify that the incoming request path matches the defined parameters.

Issue: A different Rewrite Origin URL is applied first. Cause: Priority ordering conflict. Fix: Assign a lower priority value to the entry you want processed first.

Issue: Origin returns 404 after rewrite. Cause: Target URI does not exist on the origin. Fix: Confirm that the target path is valid and reachable at the origin server.

Last updated

Was this helpful?