Next.js Runtime v5:Custom headers for different branch is not working

Support
1

The following URL procedure worked in V4 runtime, but did not work when tested in V5 runtime.
Should we assume that this feature is not yet implemented?
Note that the _headers file was placed under the .next directory.

2

You need to specify the headers in your next config as a standard Next.js site.

3

Hi, hrishikesh.

Thanks for answering.
I understand about the standard Header. So what about the BASIC authentication provided by Netlify?
I have set it up using the instructions in the following URL.
I have the _header file placed under the .next directory for a specific Branch Build.
Is there any way to do something similar to this with V5 runtime?

4

You will have to do just like you’d do it natively with Next.js on any other platform, for example: How To Add HTTP Basic Auth to Next.js - Vance Lucas

Or you can also use Netlify Edge Functions.

5

Thanks again for answering my question.

Um, I still need to change my method.
I will try to come up with a system that works for my product. Thank you.