From 9e789a1ccf9bc7ea56dd9430880d87622bb1cdb7 Mon Sep 17 00:00:00 2001 From: Ron Petrusha Date: Fri, 20 Oct 2017 15:31:03 -0700 Subject: [PATCH] Checked quirked box, fixed bad fencing (#530) * Checked quirked box, fixed bad fencing * Update wcf-binding-with-the-transportwithmessagecredential-security-mode.md --- ...ith-the-transportwithmessagecredential-security-mode.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Documentation/compatibility/wcf-binding-with-the-transportwithmessagecredential-security-mode.md b/Documentation/compatibility/wcf-binding-with-the-transportwithmessagecredential-security-mode.md index 1b7c557..1feb93c 100644 --- a/Documentation/compatibility/wcf-binding-with-the-transportwithmessagecredential-security-mode.md +++ b/Documentation/compatibility/wcf-binding-with-the-transportwithmessagecredential-security-mode.md @@ -10,18 +10,19 @@ Transparent Not planned ### Change Description -Beginning in the .NET Framework 4.6.1, WCF binding that uses the TransportWithMessageCredential security mode can be setup to receive messages with unsigned "to" headers for asymmetric security keys. +Beginning in the .NET Framework 4.6.1, WCF binding that uses the TransportWithMessageCredential security mode can be set up to receive messages with unsigned "to" headers for asymmetric security keys. By default, unsigned "to" headers will continue to be rejected in .NET 4.6.1. They will only be accepted if an application opts into this new mode of operation using the Switch.System.ServiceModel.AllowUnsignedToHeader configuration switch. Because this is an opt-in feature, it should not affect the behavior of existing apps. -- [ ] Quirked +- [X] Quirked - [ ] Build-time break ### Recommended Action Because this is an opt-in feature, it should not affect the behavior of existing apps. To control whether the new behavior is used or not, use the following configuration setting: -``` + +```xml