Azure / Azure/api-management-developer-portal
Allow URL routes other than root
- Dominant language
- TypeScript
- Stars
- 545
- Forks
- 360
- PR merge metrics
- No merged PRs in 30d
Description
**Every bug report should have precise description and reproduction steps; console traces or source code references are appreciated.**
**For assistance requests, contact Azure support or submit a post [on Stack Overflow](http://aka.ms/apimso). We don't provide support through GitHub Issues. Feature requests can be raised [on the Azure Feedback Forum](https://aka.ms/apimwish).**
## Bug description
We've configured the backendUrl for the dev portal, after the deployment of the static website in storage account, we've noticed that the home url couldn't load the css files, and it's being constantly redirected to the base url of the portal instead of the backendUrl that we configured.
## Reproduction steps
1. Go to 'https://{{ baseUrl }}/portal-apim'
2. Open browser console
3. See error "404 Resource Not Found" https://{{ baseUrl }}/styles/theme.css
## Expected behavior
The beautiful portal site should be loaded with all wwwroot assets.
## Is your portal managed or self-hosted?
Self-hosted
## Release tag or commit SHA (if using self-hosted version)
[e.g., release tag `2.8.0`]

Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the /portal-apim URL and inspecting the browser console and network requests for the missing /styles/theme.css asset. Trace how the configured backendUrl and base route are applied to navigation and wwwroot asset paths; done means the portal loads from the non-root route without redirecting assets to the base URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- cloud, frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100