You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Search engine: google.com
- Search phrase: "When working with Google Auth, and more specifically the Sign In ... disable the following header that are set by Nuxt Security automatically"
- Result page: https://www.google.com/search?q=When+working+with+Google+Auth%2C+and+more+specifically+the+Sign+In+...+disable+the+following+header+that+are+set+by+Nuxt+Security+automatically
- First result: https://nuxt-security.vercel.app/documentation/advanced/faq
Nuxt Security Version
v2.1.5
Default setup used?
Yes, the bug happens even if the security option is not customized
Security options
Reproduction
You can directly go to this page: https://nuxt-security.vercel.app/documentation/advanced/faq
Or you can search through google with the phrase: "When working with Google Auth, and more specifically the Sign In ... disable the following header that are set by Nuxt Security automatically"
Description
When we click a search result from Google to go to the FAQ, the link leads to an empty page.
Ok, got it
I think you can submit the site to Google for reindexing?
And yes, maybe a redirect of /documentation/** to /**. Either via Nuxt or via Vercel?
Environment
Nuxt Security Version
v2.1.5
Default setup used?
Yes, the bug happens even if the security option is not customized
Security options
Reproduction
You can directly go to this page: https://nuxt-security.vercel.app/documentation/advanced/faq
Or you can search through google with the phrase: "When working with Google Auth, and more specifically the Sign In ... disable the following header that are set by Nuxt Security automatically"
Description
When we click a search result from Google to go to the FAQ, the link leads to an empty page.
Additional context
This links seems to be working fine: https://nuxt-security.vercel.app/advanced/faq
--
I have seen that it was decided to be added to the FAQ in this issue, and that's why I decided to open an issue in this repo.
Logs
The text was updated successfully, but these errors were encountered: