Skip to content
This repository has been archived by the owner on Nov 4, 2024. It is now read-only.

This site returned an HTTP status code other than 200 (OK), which may cause its results to be inaccurate. #265

Open
demogit-code opened this issue Dec 17, 2021 · 7 comments

Comments

@demogit-code
Copy link

Could this be explained more in the FAQ,
and maybe with options on how to deal with that,
and how to interpret the results?

@gene1wood
Copy link
Contributor

Sure, what URL did you hit and what status code and response did you get back?

@gene1wood
Copy link
Contributor

@demogit-code what URL did you hit and what status code and response did you get back?

@demogit-code
Copy link
Author

i notice this with sites behind htaccess, with for example only https, but observatory also says http problem and others

hth

@gene1wood
Copy link
Contributor

Ok, so it sounds like this error gets triggered when you point observatory at a site that is served over HTTPS but not over HTTP? If so, does anyone know of an example of this that we can look at?

@Mth0158
Copy link

Mth0158 commented Feb 8, 2024

Hi @gene1wood ,
I am having the same issue on my personal website: https://mathieu-eustachy.com/, I do not understand why it raises this error. I am responding with an HTTP 200 when going to the mentioned url.
image

@gene1wood
Copy link
Contributor

@Mth0158 Not, sure I'm getting a 500 when I curl your site

curl -i https://mathieu-eustachy.com/
HTTP/2 500 
date: Thu, 08 Feb 2024 17:03:04 GMT
content-type: text/plain
content-length: 182
x-request-id: 71845484-9f72-418c-8ba7-6224b269939e
strict-transport-security: max-age=31536000
x-request-id: 71845484-9f72-418c-8ba7-6224b269939e
x-runtime: 0.005055

500 Internal Server Error
If you are the administrator of this website, then please read this web application's log file and/or the web server's log file to find out what went wrong.

And a 500 when I check it here : https://httpstatus.io/

@Mth0158
Copy link

Mth0158 commented Feb 9, 2024

@gene1wood it was my fault, the app was failing to get the HTTP Accept-Language header from your request and was therefore raising. I corrected it this morning and now it works fine. I did not think of using curl to fetch my website.

Maybe the issue was kind of the same for the author?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants