2017-04-18 07:52:04 +08:00
|
|
|
## Error codes for maxRequestLength or maxReceivedMessageSize are different
|
2017-04-06 04:52:19 +08:00
|
|
|
|
|
|
|
### Scope
|
|
|
|
Edge
|
|
|
|
|
|
|
|
### Version Introduced
|
|
|
|
4.5
|
|
|
|
|
|
|
|
### Source Analyzer Status
|
|
|
|
Not planned
|
|
|
|
|
|
|
|
### Change Description
|
|
|
|
|
2017-04-21 02:19:05 +08:00
|
|
|
Messages in WCF web services hosted in Internet Information Services (IIS) or
|
|
|
|
ASP.NET Development Server that exceed maxRequestLength (in ASP.NET) or
|
|
|
|
maxReceivedMessageSize (in WCF) have different error code
|
|
|
|
|
|
|
|
The HTTP status code has changed from 400 (Bad Request) to 413 (Request Entity
|
|
|
|
Too Large), and messages that exceed either the maxRequestLength or the
|
|
|
|
maxReceivedMessageSize setting throw a
|
|
|
|
<xref:System.ServiceModel.ProtocolException?displayProperty=name> exception.
|
|
|
|
This includes cases in which the transfer mode is Streamed.
|
2017-04-06 04:52:19 +08:00
|
|
|
|
|
|
|
- [ ] Quirked
|
|
|
|
- [ ] Build-time break
|
|
|
|
|
|
|
|
### Recommended Action
|
2017-04-21 02:19:05 +08:00
|
|
|
|
|
|
|
This change facilitates debugging in cases where the message length exceeds the
|
|
|
|
limits allowed by ASP.NET or WCF.
|
2017-04-06 04:52:19 +08:00
|
|
|
|
|
|
|
You must modify any code that performs processing based on an HTTP 400 status code.
|
|
|
|
|
|
|
|
### Affected APIs
|
|
|
|
* Not detectable via API analysis
|
|
|
|
|
|
|
|
### Category
|
|
|
|
Windows Communication Foundation (WCF)
|
|
|
|
|
2017-04-18 07:52:04 +08:00
|
|
|
<!-- breaking change id: 45 -->
|