Internal Choreo URL is shown in the browser URL when accessing sub directories and there is no ending /

[dineshjweerakkody]

Description

instead of the domain name, internal Choreo hostname is shown in the browser URL when entered the URL manually and redirect happens.

Steps to Reproduce

Open a browser tab and enter the following URL. Please note that there is no / at the end.
https://wso2.com/api-platform/docs/api-gateway/observability/tracing/alternative-backends

This redirects you to
https://28469332-f803-4724-9995-c05d3f053038.e1-us-east-azure.choreoapps.dev/api-gateway/observability/tracing/alternative-backends/

Version

Platform GW Documantation

Environment Details (with versions)

No response

[wso2-engineering-bot]

@wso2-engineering-bot create a PR for this issue following repo conventions

[wso2-engineering-bot]

AI Agent Analysis

This issue requires manual review and cannot be fixed automatically. Here's my analysis:

Problem Summary

When accessing documentation URLs without a trailing slash (e.g., https://wso2.com/api-platform/docs/api-gateway/observability/tracing/alternative-backends), the browser redirects to an internal Choreo hostname (https://28469332-f803-4724-9995-c05d3f053038.e1-us-east-azure.choreoapps.dev/...) instead of the public domain.

Root Cause

This is a site_url configuration issue in mkdocs.yml. When MkDocs encounters a directory URL without a trailing slash, it automatically redirects to add the trailing slash, using the configured site_url to construct the redirect URL. If the site_url is set to (or overridden with) the internal Choreo URL during deployment, that internal URL gets exposed to users.

Current Configuration

• Master branch site_url: https://apim.docs.wso2.com/en/4.7.0/
• User-accessible URL: https://wso2.com/api-platform/docs/...
• Redirect showing: Internal Choreo URL

Required Fix

1. Verify the correct public site_url: Determine whether the documentation should use https://apim.docs.wso2.com/ or https://wso2.com/api-platform/docs/ as the canonical URL
2. Update mkdocs.yml: Set the site_url to the correct public domain
3. Check deployment configuration: Ensure CI/CD pipelines or deployment scripts aren't overriding the site_url with the internal Choreo URL during build/deployment

Why This Requires Manual Review

• Modifying the site_url configuration requires understanding the intended deployment architecture and public URL structure
• May require coordination with infrastructure/deployment teams to ensure the Choreo deployment uses the correct site_url
• This is a configuration change that affects all documentation redirects and canonical URLs

Recommended Action

A team member with knowledge of the documentation deployment architecture should:

1. Review the deployment configuration for the site at wso2.com/api-platform/docs/
2. Update the site_url in mkdocs.yml (for the appropriate version branches) to match the public domain
3. Verify deployment scripts don't override this configuration with internal Choreo URLs

---

Note: The path mentioned in the issue (api-gateway/observability/tracing/alternative-backends) does not exist in the current documentation structure. Observability and tracing documentation is located at monitoring/observability/traces/. This may be an old URL or require a separate redirect configuration if it's a legacy path.