You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pre-v5.0.0 versions os Swashbuckle.AspNetCore allowed to set the base-path dynamically using a preserialize filter. This allowed to generate the proper paths behind a reverse-proxy, by doing this:
From v5.0.0 the filter gets an OpenApiDocument instead of a SwaggerDocument and it doesn't have a base-path property. Is there an alternative to enable this functionality?
I have a variable prefix, because my reverse-proxy that allows to access a variety of devices. When accessing the device directly, I can access my API via /api/v1/..., but when using the reverse-proxy I have /device//api/v1/.... I would also like to access the Swagger UI via /device//swagger.
The text was updated successfully, but these errors were encountered:
In Swagger/OpenAPI v3 the structure of the doc has changed a bit. The path has moved into the servers property. Take a look a the following readme section for some inspiration:
The pre-v5.0.0 versions os Swashbuckle.AspNetCore allowed to set the base-path dynamically using a preserialize filter. This allowed to generate the proper paths behind a reverse-proxy, by doing this:
From v5.0.0 the filter gets an
OpenApiDocument
instead of aSwaggerDocument
and it doesn't have a base-path property. Is there an alternative to enable this functionality?I have a variable prefix, because my reverse-proxy that allows to access a variety of devices. When accessing the device directly, I can access my API via /api/v1/..., but when using the reverse-proxy I have /device//api/v1/.... I would also like to access the Swagger UI via /device//swagger.
The text was updated successfully, but these errors were encountered: