Error 500 But Full page is loaded

Uptrends Monitoring is repoting that the website is returning 500 persistently but they also receive the full payload of HTML content.

Other tests and manual browser testing shows 200, as expected. Any clue why uptrends crawlers would be getting that?

Response headers:
Date: Wed, 20 Mar 2019 15:25:35 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Set-Cookie: __cfduid=d3b891ebd7d4aa8d706328c4fc16cf8181553095534; expires=Thu, 19-Mar-20 15:25:34 GMT; path=/; domain=.wisp’net; HttpOnly; Secure
X-Powered-By: PHP/7.2.7,ASP.NET
Link: <http.//wisp’net/wp-json/>; rel=“https.//api’w’org/”,<http.//wisp’net/>; rel=shortlink
Expect-CT: max-age=604800, report-uri=“https.//report-uri’Cloudflare’com/cdn-cgi/beacon/expect-ct”
Server: Cloudflare
CF-RAY: 4ba8b311ce50992b-LAX

(Note that some http links above are mutated; with a dot instead of colon; and apostrophe instead of dots) #annoying #newbie #filter

Those are the Response Headers from Uptrends? Somewhere in the headers should be the HTTP response code. It’s pretty hard to get a 200 and then call it a 500. I use UptimeRobot and they know what a 200 is. Maybe you should check with Uptrends.

@sdayman Thanks for the response.

Agreed on the response code missing from the header. Here’s a screenshot of their log which shows it’s getting 500 along with content.

Fyi- Uptrends support has been notified but doesn’t have any specific feedback as of yet. I created an account on their system to get the log details.

1 Like

Correction, here is the status from Uptrends showing the HTTP 500 status code along with a full response.

This topic was automatically closed after 14 days. New replies are no longer allowed.