No user-agent header in OpenNext on CF Workers
Hey!
I've just migrated my app from next-on-pages to OpenNext and stumbled upon an interesting thing. All requests coming from the backend part of the app don't have the User-Agent header.
Only discovered that it's a problem for me when I enabled a rule on the Cloudflare side to cut off all requests with no user-agent (helps against some bots). I found out that the next-on-pages apps still work fine, but the OpenNext ones are crushing.
Does anyone know if that's a OpenNext specific behaviour or it's rather something that comes with Cloudflare Workers (meaning that next-on-pages work on Cloudflare Pages, so they might forward the user-agent header under the hood).
I've just migrated my app from next-on-pages to OpenNext and stumbled upon an interesting thing. All requests coming from the backend part of the app don't have the User-Agent header.
Only discovered that it's a problem for me when I enabled a rule on the Cloudflare side to cut off all requests with no user-agent (helps against some bots). I found out that the next-on-pages apps still work fine, but the OpenNext ones are crushing.
Does anyone know if that's a OpenNext specific behaviour or it's rather something that comes with Cloudflare Workers (meaning that next-on-pages work on Cloudflare Pages, so they might forward the user-agent header under the hood).
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
87,353Members
Resources
Similar Threads
Was this page helpful?
