-
Notifications
You must be signed in to change notification settings - Fork 21
Closed
Labels
p1We will address this soon and will provide capacity from our team for it in the next few releases.We will address this soon and will provide capacity from our team for it in the next few releases.
Description
What information was incorrect, unhelpful, or incomplete?
When testing a website on non-standard ports, the 'redirection-to-https' test fails even if the site is already using HTTPS. In fact, a 400 'Bad Request' error message is returned because an HTTPS site is being requested over HTTP.
To reproduce the problem, you can try it on any site, here is an example:
npx @mdn/mdn-http-observatory 37.72.165.185:8443
Output:
[...]
"redirection": {
"expectation": "redirection-to-https",
"pass": false,
"result": "redirection-missing",
"scoreModifier": -20,
"destination": "http://37.72.165.185:8443/",
"redirects": false,
"route": [
"http://37.72.165.185:8443/"
],
"statusCode": 400
[...]
What did you expect to see?
I expect that in cases where the tested website is already using HTTPS, the 'redirection-to-https' test will show a result of pass: true.
Do you have any supporting links, references, or citations?
No response
Do you have anything more you want to share?
No response
Metadata
Metadata
Assignees
Labels
p1We will address this soon and will provide capacity from our team for it in the next few releases.We will address this soon and will provide capacity from our team for it in the next few releases.