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
It would be great to have a URL pattern configuration option that determines which pages the crawler can visit during the static page build-time prerendering phase.
I have an app where hooks.js redirects users to an authentication flow based on URL prefixes. It would be great to be able to exclude entire URL targets that start with a sub-pattern (eg. /restricted/ or /auth/).
Is this possible to do currently in some way that I didn't find in the documentation?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
It would be great to have a URL pattern configuration option that determines which pages the crawler can visit during the static page build-time prerendering phase.
I have an app where hooks.js redirects users to an authentication flow based on URL prefixes. It would be great to be able to exclude entire URL targets that start with a sub-pattern (eg. /restricted/ or /auth/).
Is this possible to do currently in some way that I didn't find in the documentation?
Beta Was this translation helpful? Give feedback.
All reactions