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
To avoid terminating-https MITM cert management and the scary dialogs that come with that, we'll opt-in via http://localhost urls that are forced to https on the outgoing end. I haven't quite managed how I'll facilitate just-in-time url replacement in client configs to avoid every dev being required to run this tool...for future us.
So instead of https://pkgs.dev.azure.com/a?b=c you would point nuget to http://127.0.0.1?url=pkgs.dev.azure.com/a?b=c
The text was updated successfully, but these errors were encountered:
Managing certs for MITM can be a PITA. Instead, have a normal HTTP(s?) endpoint for redirection.
From https://github.com/zjrunner/prism:
So instead of
https://pkgs.dev.azure.com/a?b=c
you would pointnuget
tohttp://127.0.0.1?url=pkgs.dev.azure.com/a?b=c
The text was updated successfully, but these errors were encountered: