robots.txt | robots.txt middleware for express/connect to server | Runtime Evironment library

Navigating within a Vaadin UI will change the URL in your browser, but it will not necessarily create a browser request to that exact URL, effectively bypassing the access control defined by Spring security for that URL. As such, Vaadin is really not suited for the request URL-based security approach that Spring provides. For this issue alone you could take a look at my add-on Spring Boot Security for Vaadin which I specifically created to close the gap between Spring security and Vaadin.

But while creating two distinct Spring security contexts based on the URL is fairly easy, this - for the same reason - will not work well or at all with Vaadin. And that's something even my add-on couldn't help with.

Update: As combining both security contexts is an option for you, I can offer the following solution (using my add-on): Starting from the Keycloak example, you would have to do the following:

1. Change WebSecurityConfig to also add your DB-based AuthenticationProvider. Adding your UserDetailsService should still be enough. Make sure to give every user a suitable role.
2. You have to remove this line from application.properties: codecamp.vaadin.security.standard-auth.enabled = false This will re-enable the standard login without Keycloak via a Vaadin view.
3. Adapt the KeycloakRouteAccessDeniedHandler to ignore all test views that shouldn't be protected by Keycloak.

I already prepared all this in Gitlab repo and removed everything not important for the main point of this solution. See the individual commits and their diffs to also help focus in on the important bits.

The issue is on line:

Thanks to @CBroe's guidance, I managed to make the social media (Facebook and Twitter) crawlers work (without using Angular Universal, Scully, Prerender.io, etc) for an Angular 11 SPA - Single Page Application, which I'm hosting on a shared hosting server.

The issue I had in the question above was in .htaccess.

This is my .htaccess (which works as expected):

Your path:

Did you tried the following structure for your Nuxt app?

The key line in the log is this one

Because routing for react app is client route. If you go directly to /map/some-thing, nginx will try to redirect it to /index.php which belongs to WP. So it'll throw 404 not found.

To fix it, you need to config your nginx, redirect every request of /map to /map/index.html. Then, react app will work as expected.

Maybe this config will help:

This is not really an answer, but I think it can give you some useful feedback and I couldn't have written this in a comment.

I tried a minimal reproducible test that should be equivalent to your case:

you need to ignore robots.txt file e.g.

wget -r -l 1 -e robots=off http://moss.stanford.edu/results/1/XXXXXXXXXX/