To explain a bit further this question of private page.
Weweb is prerendering all your pages. This pages may contains some static content (from static collection, or directly the text you put in an element without binding for ex) and some dynamic content (for example a call to your API).
If your API is secure, and someone not authenticate go to your page, they will only see the static part, and not the dynamic part (as the API will answer 401 or 403)
Because sometimes the static part need also to be secure, when you declare a private page, Weweb will check the authorization on this page when you navigate (their is a call retrieving all the “weweb” data from this page). For that it calls your authentification end point. If weweb server and your auth server are far away, and you also are far from Weweb server, the answer time can start to be long because each exchange add a noticeable delay.
Until Weweb handle localization, and this behavior is a problem for you, you can handle yourself this part.
- Double check that you do not have any secure details on the static part, and that any sensitive data is retrieve through a secure dynamic endpoint
- Let the page public
- Add a onLoad trigger which will check authorization on the page, and redirect to login page or homepage if not authorized.
This is a “bit” less secure, as static info will be available, but most of the usecase this is completly ok.