I spent a day or more researching this so that I could use Swagger-UI in my ASP.NET Core API which is used with a reverse-proxy and virtual directory. In the end found Swagger-UI requires relative URLs to start with a period. Related to https://github.com/swagger-api/swagger-ui/issues/4107
Hoping this documentation note will help others.
When creating a new PR, please do the following and delete this template text:
* Reference the issue number if there is one:
Fixes #Issue_Number
> The "Fixes #nnn" syntax in the PR description causes
> GitHub to automatically close the issue when this PR is merged.
* overview
* whats new to end
* fix migration node
* split fundamentals, move to end
* glob & loc, get started
* security node name
* security section
* azure, client-side, host
* several more sections
* redistribute tutorials
* proofread fixes
* move how to download section
* index files delete and redirect
* fix errors
* reorder some nodes
* scott feedback, flatten main tutorials node
* fix missed feedback items + other issues
* unflatten tutorials node
* move 'how to download'
* more tutorials node tweaks
* standardize view sample links
* db --> DB
* fix build error
* remove link from a parent node
* streamline node names
* xref links
* typos
* typo
* typos and revert some xref links
* scott feedback
* scott feedback
* feedback
* change node name
* safe storage-->protect
* Update Swagger tutorials for 2.1
* Improve PMC instructions
* Verbiage tweaks
* Fix code highlighting in NSwag tutorial
* Remove unnecessary screenshots
* Apply 2.1 moniker to Swashbuckle tutorial
* Replace line numbers with region name
* NSwag 2.1 sample app updates
* Update Data annotations section of NSwag doc
* Add tip to NSwag doc
* Minor tweaks
* NSwag doc updates
* Fix API ref links
* Add section for adding API info
* Add sentence to Customize section
* Convert H2 heading to H3
* React to feedback
Scott Addie
Luke Latham
Robb Schiefer
Tom Dykstra
Matt Millican
Scott Addie
Rick Anderson
Rico Suter