You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off, best practices say do not do automatic redirects like that on your web site. Second, fpnd network links are purposely "tight" so we do not take over the default route on a user host. Instead, we route only a few protocols (ie, http/https and dns/dot) between specific ports, which does not take into account working around upstream sites doing such redirects. This does not affect https requests, only http requests to a site doing automatic redirects of 80=>443. Using http with a site that only offers http should still work (and is still horribly insecure).
The text was updated successfully, but these errors were encountered:
First off, best practices say do not do automatic redirects like that on your web site. Second, fpnd network links are purposely "tight" so we do not take over the default route on a user host. Instead, we route only a few protocols (ie, http/https and dns/dot) between specific ports, which does not take into account working around upstream sites doing such redirects. This does not affect
https
requests, onlyhttp
requests to a site doing automatic redirects of 80=>443. Usinghttp
with a site that only offers http should still work (and is still horribly insecure).The text was updated successfully, but these errors were encountered: