This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 52%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETY%3C/text%3E%3C/svg%3E)
Hi,
Question:
I published one api on URL http://test-api.azurewebsites.net and I am able to browse the URL which seems fine.
Is it possible: If I need URL in this way whatever is on root want to see on this path?
http://test-api.azurewebsites.net/LandingFolder
Hello @Tariq Younas
Are you looking for virtual directories and path mappings?
https://stackoverflow.com/questions/63522346/how-to-enforce-azure-virtual-application-base-path
Thanks for the reply AndriyBilous.
will it open like
http://test-api.azurewebsites.net/site1
http://test-api.azurewebsites.net/site2
after browsing http://test-api.azurewebsites.net/site1 what URL will remain on the top?
http://test-api.azurewebsites.net/site1
OR
http://test-api.azurewebsites.net
root path (/) mapped to D:\home\site\wwwroot
virtual directory and its corresponding physical path relative to the website root (D:\home).
If you configure virtual directories after browsing http://test-api.azurewebsites.net/site1, this URL remain on top
II published my site at wwwroot/site1
Now I want to see http://test-api.azurewebsites.net/site1, In this scenario what will be the virtual and physical paths?
virtual path - /site1
physical paths - site\site1
@Tariq Younas were you able to published your site at wwwroot/site1?