You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usually, Apache doesn't pass the Authorization header by default to fgci. We should look into if we can add it to the WordPress rules for .htaccess, or somethign like that. This problem has existed on a lot of sites using apache that I've tested.
The text was updated successfully, but these errors were encountered:
Incidentally, something like WordPress/application-passwords@16af809 can test for whether the site's server is killing the authentication header, or whether it's behaving properly -- if it's worth making a general purpose tester or something.
Usually, Apache doesn't pass the Authorization header by default to fgci. We should look into if we can add it to the WordPress rules for .htaccess, or somethign like that. This problem has existed on a lot of sites using apache that I've tested.
The text was updated successfully, but these errors were encountered: