Knoobie

Isn't that already possible with https://github.com/vaadin/flow/blob/master/flow-server/src/main/java/com/vaadin/flow/server/StaticFileHandlerFactory.java and custom `StaticFileHandler` because your method is `protected`?

That is expected. Any link since v23 that has no `router-ignore` attribute is handled by the Vaadin Router. It's documented in the [Migration Guide](https://vaadin.com/docs/latest/upgrading/essential-steps/#miscellaneous-changes).

@svein-loken Keep in mind that this usage of executeJs leaves you open for attacks. You should convert this to the usage shown here: https://vaadin.com/docs/latest/security/advanced-topics/vulnerabilities/#running-custom-javascript

I think he is talking about something like RP-Initiated logout from the Oauth Spec - which is not part of flow and has to be implemented by himself.

This is to be expected - see https://stackoverflow.com/a/58199008/1662997

I'm in favor of reducing complexity, just wondering if the old `components` structure could be re-used somehow / would still works after this? Because for me it's really helpful to...

I would suggest to post your nginx and push configuration.

I don't see anything related to push in the configuration. Cuba has a example for nginx that you could try: https://doc.cuba-platform.com/manual-latest/server_push_settings.html#server_push_settings_using_proxy - important is the part about `upgrade` I'm more...

> I believe this could be in the documentation. How to configure a reverse proxy should be an important topic inside the docs (cc: @tarekoraby)

@kagian Please share it, if you wanna see steady progress in this topic.