Programmatically catching 5.2 error protection

  • Hi,
    I have a script that would regular pinging all my wordpress sites I am supporting (60+ sites), and it tries to catch any non-2xx http return code for problem.

    With the new 5.2 error protection which now giving “The site is experiencing technical difficulties….” with a 200 http return code. What is the best way to capture the error now?

    I know a lot of 3rd ping service would also try to catch non-2xx code. The new error protection handling seems to make this a lot difficult.

    Peter

Viewing 2 replies - 1 through 2 (of 2 total)
  • Tyler

    (@tylerthedude)

    Hi Peter,

    Would you mind attaching the script you are running to ping your sites? This will give me a better understanding as to the code behind this process.. typically sites that run on WordPress or not will still return an HTTP request code that will be visible to anyone on the back-end of the site.

    This will be found in the site’s access log, as it captures all of the HTTP requests sent to the site and your webserver will throw it into this log. You can find the requests through here, but that means you will need to access each site you’re wanting to test and check the access logs accordingly.

    Writing this into the script will require quite a bit more of conditional statements, but if you choose to proceed down this route then it will be necessary.

    Thanks,
    Tyler

    • This reply was modified 5 years, 3 months ago by Marius L. J.. Reason: Removed signature
    Timothy Jacobs

    (@timothyblynjacobs)

    @quickpick The intention is for Recovery Mode to return a 500 status code. Could you check if your site is outputting any content before the error HTML? We might be able to detect if it is if you can send a screenshot of the full page as well.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Programmatically catching 5.2 error protection’ is closed to new replies.