This repository has been archived by the owner on Nov 4, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 170
HTTP to HTTPS redirection not validated on subdomain #451
Comments
This can sometimes occur if there’s a series of redirects, especially in
circumstances involving SSO or other intercept-redirect auth systems. When
you curl -v https, does it return another Location header?
…On Thu, Sep 16, 2021 at 07:47 deastr ***@***.***> wrote:
We have an internal website at https://sub.company.com being tested with
Observatory. Web server set to redirect HTTP requests to HTTPS but for some
reason Observatory says that it isn't so. When I visit
http://sub.company.com with browser it gets redirected to
https://sub.company.com. I tried curl and also got 301 result. Am I
misunderstanding this rule or doing something wrong or does it not apply to
subdomains?
Here's the curl output:
curl -v http://sub.company.com/
* Trying xxx...
* Connected to sub.company.com (xxx) port 80 (#0)
> GET / HTTP/1.1
> Host: sub.company.com
> User-Agent: curl/7.79.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 301 Moved Permanently
< Content-Type: text/html; charset=UTF-8
< Location: https://sub.company.com/
< Server:
< Date: Thu, 16 Sep 2021 13:40:08 GMT
< Content-Length: 161
<
<head><title>Document Moved</title></head>
<body><h1>Object Moved</h1>This document may be found <a HREF="https://sub.company.com/">here</a></body>* Connection #0 to host sub.company.com left intact
Both HTTP and HTTPS versions of sub.company.com and company.com doesn't
have IPV6 enabled, I checked with https://ipv6-test.com/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#451>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAWUDEIILTS3RAQBGSJSJ3UCH7PRANCNFSM5EE56R6A>
.
|
No, it's 200:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have an internal website at https://sub.company.com being tested with Observatory. Web server set to redirect HTTP requests to HTTPS but for some reason Observatory says that it isn't so. When I visit http://sub.company.com with browser it gets redirected to https://sub.company.com. I tried curl and also got 301 result. Am I misunderstanding this rule or doing something wrong or does it not apply to subdomains?
Here's the curl output:
Both HTTP and HTTPS versions of sub.company.com and company.com doesn't have IPV6 enabled, I checked with https://ipv6-test.com/
The text was updated successfully, but these errors were encountered: