Paulo Lopes

We now have support for openapi 3.1 in the new module vertx-web-openapi-router

CORS implementation has been reviewed to follow the OWASP recommendations. I'd recommend against premature optimizations

@fbuetler I believe you're right. They should be copied if I'm not mistaken.

Now that we're finishing vert.x 5.0.0 and given that this would introduce a behavior change, a PR is ready that follows what has been discussed in this issue.

Note that we don't cover `flow` anymore as vertx-auth has been improved to accept any kind of flow. In the past when dealing with `auth_code` for frontend UI and for...

Closing for inactivity

Closing as the current implementation gives users a best effort in ensuring that state is correct. For better control use flush and a relational database as backend.

The new openapi router, expects user to provide the openapi document. This is to avoid acidental fetch if insecure resources from the network that could expose an application to a...

@nbrendah i believe the request is to improve the basic documentation with a more complex example and use case.

Yes, that and allowing the user to set the order of the algorithms (to reduce the failure tests) should fix it.