Anthony Corcutt

Hi, cookies do not work too well with this approach so auth would be best done client side, there is an example that uses headers which should support cookies https://next-multi-host.vercel.app/headers...

Seems its running dynamic rewrites first on SSR last on client: Try with js on/off: https://next-multi-host-pdicl46ht-acorcutt.vercel.app/ https://github.com/acorcutt/next-multi-host/tree/catchall

Temporary solution using fallback rewrites and proxy catch-all route to another app or another domain of itself: ``` fallback: [ { has: [ { type: 'host', value: '(?.*)', }, ],...

Possibly related: https://github.com/vercel/next.js/blob/master/errors/rewrite-auto-export-fallback.md

It will allow different start/end syntax, but if this is something that should not be allowed I'm not sure if this should be checked inside the scanner or if it...

No it will match single tags `{tag}` but for blocks you need the prefix `{block:tag}{/block:tag}` To support `{tag}content{/tag}` you need something like this: `%r{\{([\w:]+?)(\s+(?:\w+\s*=\s*(?:"[^"]*?"|'[^']*?')\s*)*|)(\/?)\}|\{\/([\w:]+?)\s*\}}` But to support `` you will...

Yes, sorry the regex will match but I forgot the scanner also modifies `operate()` to handle the non-closed `{tag}` style. If you use the `operate()` from the default scanner you...