The swagger not working when hosting gateway in a virtual directory on IIS

[jigneshnarain]

The swagger endpoint does not update to the virtual hosted gateway. The endpoint remain "/swagger/docs". When clicking on the it open a link to the service swagger without the virtual host name.

Expected /gateway/swagger/docs/v1/servicename
Actual /swagger/docs/v1/servicename

However, when I manually navigate to the path /gateway/swagger/docs/v1/servicename, the json renders as expected.

Additionally, I tried the following but no luck.
app.UseSwaggerForOcelotUI(opt => {
opts.ServerOcelot = "/siteName/gateway" ;
})

How do I get swagger to work when hosting the gateway in a virtual directory.

[raman-m]

We don't support Swagger officially❗

But we believe it will be supported in future, see

• Add info about MMLib.SwaggerForOcelot to notsupported.rst #1429
• Does Ocelot support YAML files instead of JSON for Swagger configuration? #1904
• more discussions

We don't recommend to deploy to IIS ❕

• See IIS Gotchas