up_the_irons: Just wanted to thank you for your help (without reopening the ticket), appreciate the help!
(Wow I said "help" twice in the same sentence. I'm really not paying attention I guess, oops.)
Blink twice if you need to be rescued.
(I wondered if anyone would go there, lol)
blink = drop a packet?
brycec: no problem :)
To anyone on Windows 10 with Chrome, can you click "Customer Login" on arpnetworks.com and does it redirect to the Portal?  Had one report that it did not
up_the_irons: It definitely worked for me (3x today alone)
I will report that going to http://portal.arpnetworks.com gives me back a 301 to https://arpnetworks.com (Win10, Chrome, IPv4)
^ Going to the same URL over IPv6 serves the online portal over port 80
up_the_irons: So... your v4 and v6 listeners are configured differently ;)
iiiiiiiiiiiiiiinteresting
so portal.arpnetworks.com is actually available over port 80 on IPv6?
up_the_irons: https://pastebin.com/7mQvze6Q
And yes, yes it is.
And over v4, it redirects to the wrong site.
fml
You don't even set an HSTS header on v6:80
It's okay, up_the_irons , computers are hard.
mercutio: can you create a trello card to fix that when you get a chance ^^^
we haven't made changes for as long as I can remember, but it took a customer from NASA to point out that issue (today)
brycec: thanks I feel so much better (no...) lol
1) No HSTS headers on main website OR portal.  2) portal over v6 port 80 serves the portal instead of redirecting to 443. 3) portal over v4 port 80 redirects to main website, not portal:443
to summarise for mercutio ^
I might have noticed the issues with the portal sooner too if things ever broke down, up_the_irons :P