We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The prefix is present on some configurations of PHP with FastCGI. So I guess OAuth1 should check for both. See here: WP-API/api-console#1 (comment)
The text was updated successfully, but these errors were encountered:
Hmm I'm not sure if this is any official header and therefore should be included, I'm leaning towards no, but let's open this for discussion.
Sorry, something went wrong.
I'd like to mention that we see this regularly.
Where REDIRECT_HTTP_AUTHORIZATION is present, but HTTP_AUTHORIZATION is not.
I understand this occurs when PHP is running in FastCGI mode and the HTTP_AUTHORIZATION is set via SetEnv or .htaccess directives such as
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}
FWIW the same issue occurs in the Wordpress Basic Auth plugin.
We've handled this as described in this article: https://www.metalocator.com/wp-json-basic-auth-with-fastcgi/
No branches or pull requests
The prefix is present on some configurations of PHP with FastCGI. So I guess OAuth1 should check for both.
See here: WP-API/api-console#1 (comment)
The text was updated successfully, but these errors were encountered: