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
Another option would be to default to false, this would make the client work better with fiddler out of the box. Does this qualify as a backwards compatibility breaking change though?
We've seen more people being hit by slow initial requests due to .ProxyNOT being null then due to it being null as was seen in #809 which is the main reason for defaulting to true.
I don't think changing the default back to false would be considered a bwc breaking change, and it's the best option IMO since it takes the path of least resistance. Users who had to change the setting to false since 1.0 to work with Fiddler won't be affected, and the smaller group of users who experience slow initial requests due to it not being null (#809) still have the option to disable it.
Defaulting to false also makes sense given the name of the setting and the fact that the optional parameter (enabled) defaults to true.
Would be better to make the setting a
bool?
so that it defaults to whatever the BCL default is, but that would break bwc.The text was updated successfully, but these errors were encountered: