To convert the value into kilobytes, multiply by 1024. To allow for the 33% increase in size due to Base64 encoding, multiply your desired new maximum size value in megabytes by 4/3. These procedures are performed in the operating system of the Exchange server.Ĭhanges you save to the web.config configuration file are applied after you restart IIS. What do you need to know before you begin?Įxchange permissions don't apply to the procedures in this topic. In the backend web.config file, there's an instance of the value maxStringContentLength="102400" for the MsOnlineShellService binding that you don't need to modify.%ExchangeInstallPath%ClientAccess\Owa\web.configĢ instances of maxReceivedMessageSize="35000000" (for http and https bindings)Ģ instances of maxStringContentLength="35000000" (for http and https bindings) %ExchangeInstallPath%FrontEnd\HttpProxy\owa\web.config MaxRequestLength is an ASP.NET setting that's present in both web.config files, but isn't used by EWS, so you don't need to modify it. In the backend web.config file, there are two instances of the value maxReceivedMessageSize="1048576" for UMLegacyMessageEncoderSoap11Element bindings that you don't need to modify. %ExchangeInstallPath%ClientAccess\exchweb\ews\web.configġ4 instances of maxReceivedMessageSize="67108864" (for different combinations of http/https bindings and authentication methods) %ExchangeInstallPath%FrontEnd\HttpProxy\ews\web.config Note: You can change the same setting in IIS manager at Sites > Default Web Site > Microsoft-Server-ActiveSync or Sites > Exchange Back End > Microsoft-Server-ActiveSync and then Request Filtering in the IIS section > Edit Feature Settings in the Actions area > Maximum allowed content length (Bytes) in the Request Limits section.Īfter you change the value in IIS Manager, a new maxAllowedContentLength key is written to the corresponding Client Access or backend web.config file that's described in the table. You need to change the value on the Client Access web site and the back end web site. To change the maxAllowedContentLength value, enter a new value in bytes, and click Apply. In the results, expand requestLimits, and you'll see maxAllowedContentLength and the default value 30000000 (bytes). Verify the Features View tab is selected at the bottom, and double-click Configuration Editor in the Management section.Ĭlick the drop down arrow in the Section field, navigate to system.webServer > security and select requestFiltering. To see these values for ActiveSync on Mailbox servers in IIS Manager, perform the following steps:įor the Client Access (frontend) web site, open IIS Manager, navigate to Sites > Default Web Site and select Microsoft-Server-ActiveSync.įor the backend web site, open IIS Manager, navigate to Sites > Exchange Back End and select Microsoft-Server-ActiveSync. However, the maximum message size for ActiveSync is affected by the maxAllowedContentLength value that is applied to all web sites on the server. MaxAllowedContentLength="30000000 bytes" (not present by default see comments)īy default, there is no maxAllowedContentLength key in the web.config files for ActiveSync. %ExchangeInstallPath%ClientAccess\Sync\web.config
MaxAllowedContentLength="30000000" (not present by default see comments) %ExchangeInstallPath%FrontEnd\HttpProxy\Sync\web.config For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. For any message size limit, you need to set a value that's larger than the actual size you want enforced.
0 kommentar(er)
