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
For compatibility with a range of clients, STAC and coverages endpoints need to support URLs both with and without a trailing slash. Due to time pressure during OGC Testbed-19, this was implemented very simplistically by adding an extra api.route decorator to the implementations, e.g.
Add an optional "slash" parameter to the server.api.Api.route
decorator, a corresponding constructor parameter and field to
ApiRoute, and code to handle this field to
TornadoFramework.add_routes.
Passing slash=True causes the framework to add an additional
second route, handling the same path as the specified route
but with a suffixed "/" character.
Addresses issue #965.
For compatibility with a range of clients, STAC and coverages endpoints need to support URLs both with and without a trailing slash. Due to time pressure during OGC Testbed-19, this was implemented very simplistically by adding an extra
api.route
decorator to the implementations, e.g.In source code this is non-DRY, and in deployment it has the unfortunate effect of duplicating the generated OpenAPI documentation for every endpoint:
Slash / no-slash handling should be implemented in a way that avoids cut-and-paste source code and duplicated OpenAPI entries.
The text was updated successfully, but these errors were encountered: