3 ms·
I just recently got my company's moneymaker app into HTTPS, and it was no small feat. So much totally screwed up browser automation (read: DOM/JS interaction) a
by spacemanmatt 6y ago
I just recently got my company's moneymaker app into HTTPS, and it was no small feat. So much totally screwed up browser automation (read: DOM/JS interaction) and ad-hoc URL construction kept disrupting the HTTPS experience by attempting to redirect or fetch HTTP.
I did have the certificate and reverse proxy ready to go a full 18 months before I could finish the app migration. Someone previous developer was REALLY against relative URLs. "http://".$host.$urlPath http://".$host.$urlPath everywhere.
- spacemanmatt 6y ago...there is still a tiny bit of cleartext access, because some clients have URLs embedded in spreadsheets and support would rather not hear from all of them at once.