Should docs for Secure Web Functions use X-Require-Whisk-Auth header?

I want to activate the Secure Web Function feature on serverless functions. In the Functions docs it says to use the header X-Function-Auth and this is also what it says on my function’s settings page.

To require authentication, enable Secure Web Function. This prompts you to enter a secret token, which you will then need to provide in the X-Function-Auth header for each request

However I get a 401 response when I use this header. Instead, the example curl command uses the header X-Require-Whisk-Auth and using this header gives me access to my function.

Should the docs be updated to reflect that X-Require-Whisk-Auth is the correct header?

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

card icon
Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Sign up
card icon
Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We’d like to help.

Learn more
card icon
Become a contributor

You get paid; we donate to tech nonprofits.

Learn more
Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow – whether you’re running one virtual machine or ten thousand.

Learn more ->
DigitalOcean Cloud Control Panel
Get started for free

Enter your email to get $200 in credit for your first 60 days with DigitalOcean.

New accounts only. By submitting your email you agree to our Privacy Policy.

© 2023 DigitalOcean, LLC.