Paulo Lopes

I believe the "callback" url isn't being properly configured, I'll debug the situation, and on the meantime, you can try to do: ```java router.route().handler(SessionHandler.create(LocalSessionStore.create(vertx))); router.route("/protected/*").handler( OAuth2AuthHandler.create(vertx, githubAuth, "http://localhost:8080/callback") .withScope("profile") .setupCallback(router.route("/callback")));...

I've to be honest, this is the 1st time I've heard about this header. From what I understood from the RFC this is similar to what H2 does and we...

This is also an experimental RFC and currently only supported by Google Chrome: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/103

Depends on https://github.com/eclipse-vertx/vert.x/pull/4508

@Ludo-LM @cavallium I can imagine this feature as a new handler that takes the functionality out of the static handler. You can imagine it like: ```java router.get("/static/*") .handler(EarlyHintsHandler.create() .link(Link.create("style.css").as("style").rel("preload")) .link(Link.create("script.js").as("script").rel("preload"))...

If we don't know what kind of token it is, it is not possible for vertx-web to assert the authenticity of the token and therefore the authenticity of the user....

@madewael just a second here! I like the direction this is going, but let us concentrate on the goal. You're looking for a generic `Bearer` token handler for a custom...

I did some further tests and this also requires changes to: @return Where i get a similar exception

@alexellis Yes, I've been working on removing the sharp edges (relying on snapshot artifacts and duplicated interfaces). I'm now going a testing phase and will propose it soon

We need to update the template