Pulse can't follow 301 redirect?? about pulse

[konklone]

@noisyneighbor Can you share the website you're checking? This would make it easier to debug. You can email the URL to [email protected] if you're not comfortable posting it publicly, but I recommend just posting it publicly to make discussion easier.

[noisyneighbor]

try citgo.cdc.gov or webmail.cdc.gov Thanks Curt -

…

--- Eric Mill <[email protected]> wrote:

@noisyneighbor Can you share the website you're checking? This would make it easier to debug. You can email the URL to ***@***.*** if you're not comfortable posting it publicly, but I recommend just posting it publicly to make discussion easier. -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #800 (comment)

[konklone]

@noisyneighbor it looks like you are missing the HSTS header on the root:

$ curl --head https://webmail.cdc.gov
HTTP/1.0 302 Found
Location: https://webmail.cdc.gov/owa/
Server: BigIP
Connection: Keep-Alive
Content-Length: 0

If you're seeing something different, it might be because you're scanning from inside the firewall and have different DNS for internal services?

Right now, Pulse (and DHS) look for the HSTS header at the root, rather than at a redirect destination. If you can get the HSTS header onto the root, that would resolve this.