wp-site-health/v1/tests/authorization-header

  • To enable this test to succeed in apache or Nginx is straightforward not so in Jetty. In order to make it work I had to make some code changes and add a php script to the server as I was unable to to find a Jetty configuration solution. The test appears to have succeeded but in the log I see the following message:
    “PHP Warning: Unknown: failed to open stream: Permission denied in Unknown on line 0”
    First I’m assuming this is an expected response and second, is there a known documented Jetty solution for authorization-headers?

    Thanks for any replies…

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator Dion Hulse

    (@dd32)

    Meta Developer

    Hi @tezzerfx,

    I’m not familiar with Jetty, but I’m assuming you’re referring to https://www.eclipse.org/jetty/

    I’m not able to find much information on setting up PHP with it, other than that it uses FastCGI. I would look at finding out how to pass the Authorization header to FastCGI apps in Jetty rather than specifically with WordPress.

    I think you’re going to be better off approaching the Jetty mailing lists / support avenues rather than the WordPress forums, as I believe few people will be using it.

    “PHP Warning: Unknown: failed to open stream: Permission denied in Unknown on line 0”

    That’s not expected by WordPress, and as it’s saying Unknown on line 0 I’m assuming this is potentially being output from the php script you added, which I’m assuming you added as a auto_prepend_file definition.
    If you’ve added some custom code via that, you might find adding it to the top of wp-config.php will aid in getting some proper error messages back as to what’s failing.

    Thread Starter tezzerfx

    (@tezzerfx)

    Hello @dd32,

    Thanks for your response, I hadn’t thought to use the “auto_prepend_file” mechanism, not being a php expert, it was the perfect solution! I captured the “Authorization” header in Jetty and funneled the value to the prepend file which populated a new $_SERVER[‘HTTP_AUTHORIZATION’] field in the array. It was the Nginx solution which led me to this, and all’s working nicely & error free. So thanks again!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘wp-site-health/v1/tests/authorization-header’ is closed to new replies.