response: 413 Request Entity Too Large





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















When POSTing a request which can contain one or more files (as base64 string) I get this error response:




ERROR 2018-11-22 09:54:18,244 [13 ] Mvc.ExceptionHandling.AbpExceptionFilter - The remote server returned an unexpected response: (413) Request Entity Too Large.
System.ServiceModel.ProtocolException: The remote server returned an unexpected response: (413) Request Entity Too Large.
at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object outs, IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannelProxy.TaskCreator.<>c__DisplayClass1_0.b__0(IAsyncResult asyncResult)
--- End of stack trace from previous location where exception was thrown ---
at ...




I have searched on how to resolve this but I get redirected to WCF solutions all the time.



I have added the following to the web.config of my WebApi project but it doesn't seem to make a difference.



<configuration>
<system.webServer>
....
<asp>
<limits maxRequestEntityAllowed="2147483648"/>
</asp>
<serverRuntime uploadReadAheadSize="2147483647" />
</system.webServer>
</configuration>


Can anyone help me or point me to the right resource?










share|improve this question































    0















    When POSTing a request which can contain one or more files (as base64 string) I get this error response:




    ERROR 2018-11-22 09:54:18,244 [13 ] Mvc.ExceptionHandling.AbpExceptionFilter - The remote server returned an unexpected response: (413) Request Entity Too Large.
    System.ServiceModel.ProtocolException: The remote server returned an unexpected response: (413) Request Entity Too Large.
    at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
    at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
    at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object outs, IAsyncResult result)
    at System.ServiceModel.Channels.ServiceChannelProxy.TaskCreator.<>c__DisplayClass1_0.b__0(IAsyncResult asyncResult)
    --- End of stack trace from previous location where exception was thrown ---
    at ...




    I have searched on how to resolve this but I get redirected to WCF solutions all the time.



    I have added the following to the web.config of my WebApi project but it doesn't seem to make a difference.



    <configuration>
    <system.webServer>
    ....
    <asp>
    <limits maxRequestEntityAllowed="2147483648"/>
    </asp>
    <serverRuntime uploadReadAheadSize="2147483647" />
    </system.webServer>
    </configuration>


    Can anyone help me or point me to the right resource?










    share|improve this question



























      0












      0








      0








      When POSTing a request which can contain one or more files (as base64 string) I get this error response:




      ERROR 2018-11-22 09:54:18,244 [13 ] Mvc.ExceptionHandling.AbpExceptionFilter - The remote server returned an unexpected response: (413) Request Entity Too Large.
      System.ServiceModel.ProtocolException: The remote server returned an unexpected response: (413) Request Entity Too Large.
      at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
      at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
      at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object outs, IAsyncResult result)
      at System.ServiceModel.Channels.ServiceChannelProxy.TaskCreator.<>c__DisplayClass1_0.b__0(IAsyncResult asyncResult)
      --- End of stack trace from previous location where exception was thrown ---
      at ...




      I have searched on how to resolve this but I get redirected to WCF solutions all the time.



      I have added the following to the web.config of my WebApi project but it doesn't seem to make a difference.



      <configuration>
      <system.webServer>
      ....
      <asp>
      <limits maxRequestEntityAllowed="2147483648"/>
      </asp>
      <serverRuntime uploadReadAheadSize="2147483647" />
      </system.webServer>
      </configuration>


      Can anyone help me or point me to the right resource?










      share|improve this question
















      When POSTing a request which can contain one or more files (as base64 string) I get this error response:




      ERROR 2018-11-22 09:54:18,244 [13 ] Mvc.ExceptionHandling.AbpExceptionFilter - The remote server returned an unexpected response: (413) Request Entity Too Large.
      System.ServiceModel.ProtocolException: The remote server returned an unexpected response: (413) Request Entity Too Large.
      at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
      at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
      at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object outs, IAsyncResult result)
      at System.ServiceModel.Channels.ServiceChannelProxy.TaskCreator.<>c__DisplayClass1_0.b__0(IAsyncResult asyncResult)
      --- End of stack trace from previous location where exception was thrown ---
      at ...




      I have searched on how to resolve this but I get redirected to WCF solutions all the time.



      I have added the following to the web.config of my WebApi project but it doesn't seem to make a difference.



      <configuration>
      <system.webServer>
      ....
      <asp>
      <limits maxRequestEntityAllowed="2147483648"/>
      </asp>
      <serverRuntime uploadReadAheadSize="2147483647" />
      </system.webServer>
      </configuration>


      Can anyone help me or point me to the right resource?







      c# asp.net-core asp.net-core-webapi aspnetboilerplate






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 22 '18 at 11:42









      M. Mennan Kara

      8,70912734




      8,70912734










      asked Nov 22 '18 at 10:08









      JurjenJurjen

      199421




      199421
























          3 Answers
          3






          active

          oldest

          votes


















          1














          There are two limits you need to change. Kestrel and IIS.



          You can change the MaxRequestBodySize limit of Kestrel in Program.cs.



          public static IWebHost BuildWebHost(string args)
          {
          return WebHost.CreateDefaultBuilder(args)
          .UseStartup<Startup>()
          .UseKestrel(options =>
          {
          options.Limits.MaxRequestBodySize = long.MaxValue;
          })
          .UseIISIntegration()
          .Build();
          }


          And the limit for IIS can be changed in web.config:



          <?xml version="1.0" encoding="utf-8"?>
          <configuration>
          <system.webServer>
          <security>
          <requestFiltering>
          <requestLimits maxAllowedContentLength="2147483648" />
          </requestFiltering>
          </security>
          </system.webServer>
          </configuration>





          share|improve this answer

































            0














            I think, you may need to modify your web.config then add "maxRequestLength" and "maxAllowedContentLength"



            <system.web>
            <compilation debug="true" targetFramework="4.5.2"/>
            <httpRuntime targetFramework="4.5.2" maxRequestLength="50240" executionTimeout="600"/> <!-- in Kb -->
            </system.web>
            <system.webServer>
            <security>
            <requestFiltering>
            <requestLimits maxAllowedContentLength="52428800" /> <!-- in byte (50 Mb) -->
            </requestFiltering>
            </security>





            share|improve this answer
























            • I already tried setting maxAllowedContentLength, it doesn't make a difference. I'm using .NET Core, so I'm not sure System.Web will work, specially referencing 4.5.2 as targetFramework.

              – Jurjen
              Nov 22 '18 at 11:13





















            0














            Default limit size 65 KB in WCF. Could you try to add below field inside of your binding configuration.
            <binding maxReceivedMessageSize="10485760">






            share|improve this answer
























              Your Answer






              StackExchange.ifUsing("editor", function () {
              StackExchange.using("externalEditor", function () {
              StackExchange.using("snippets", function () {
              StackExchange.snippets.init();
              });
              });
              }, "code-snippets");

              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "1"
              };
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function() {
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled) {
              StackExchange.using("snippets", function() {
              createEditor();
              });
              }
              else {
              createEditor();
              }
              });

              function createEditor() {
              StackExchange.prepareEditor({
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader: {
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              },
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              });


              }
              });














              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53428474%2fresponse-413-request-entity-too-large%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              3 Answers
              3






              active

              oldest

              votes








              3 Answers
              3






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              1














              There are two limits you need to change. Kestrel and IIS.



              You can change the MaxRequestBodySize limit of Kestrel in Program.cs.



              public static IWebHost BuildWebHost(string args)
              {
              return WebHost.CreateDefaultBuilder(args)
              .UseStartup<Startup>()
              .UseKestrel(options =>
              {
              options.Limits.MaxRequestBodySize = long.MaxValue;
              })
              .UseIISIntegration()
              .Build();
              }


              And the limit for IIS can be changed in web.config:



              <?xml version="1.0" encoding="utf-8"?>
              <configuration>
              <system.webServer>
              <security>
              <requestFiltering>
              <requestLimits maxAllowedContentLength="2147483648" />
              </requestFiltering>
              </security>
              </system.webServer>
              </configuration>





              share|improve this answer






























                1














                There are two limits you need to change. Kestrel and IIS.



                You can change the MaxRequestBodySize limit of Kestrel in Program.cs.



                public static IWebHost BuildWebHost(string args)
                {
                return WebHost.CreateDefaultBuilder(args)
                .UseStartup<Startup>()
                .UseKestrel(options =>
                {
                options.Limits.MaxRequestBodySize = long.MaxValue;
                })
                .UseIISIntegration()
                .Build();
                }


                And the limit for IIS can be changed in web.config:



                <?xml version="1.0" encoding="utf-8"?>
                <configuration>
                <system.webServer>
                <security>
                <requestFiltering>
                <requestLimits maxAllowedContentLength="2147483648" />
                </requestFiltering>
                </security>
                </system.webServer>
                </configuration>





                share|improve this answer




























                  1












                  1








                  1







                  There are two limits you need to change. Kestrel and IIS.



                  You can change the MaxRequestBodySize limit of Kestrel in Program.cs.



                  public static IWebHost BuildWebHost(string args)
                  {
                  return WebHost.CreateDefaultBuilder(args)
                  .UseStartup<Startup>()
                  .UseKestrel(options =>
                  {
                  options.Limits.MaxRequestBodySize = long.MaxValue;
                  })
                  .UseIISIntegration()
                  .Build();
                  }


                  And the limit for IIS can be changed in web.config:



                  <?xml version="1.0" encoding="utf-8"?>
                  <configuration>
                  <system.webServer>
                  <security>
                  <requestFiltering>
                  <requestLimits maxAllowedContentLength="2147483648" />
                  </requestFiltering>
                  </security>
                  </system.webServer>
                  </configuration>





                  share|improve this answer















                  There are two limits you need to change. Kestrel and IIS.



                  You can change the MaxRequestBodySize limit of Kestrel in Program.cs.



                  public static IWebHost BuildWebHost(string args)
                  {
                  return WebHost.CreateDefaultBuilder(args)
                  .UseStartup<Startup>()
                  .UseKestrel(options =>
                  {
                  options.Limits.MaxRequestBodySize = long.MaxValue;
                  })
                  .UseIISIntegration()
                  .Build();
                  }


                  And the limit for IIS can be changed in web.config:



                  <?xml version="1.0" encoding="utf-8"?>
                  <configuration>
                  <system.webServer>
                  <security>
                  <requestFiltering>
                  <requestLimits maxAllowedContentLength="2147483648" />
                  </requestFiltering>
                  </security>
                  </system.webServer>
                  </configuration>






                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Nov 22 '18 at 11:40

























                  answered Nov 22 '18 at 10:25









                  M. Mennan KaraM. Mennan Kara

                  8,70912734




                  8,70912734

























                      0














                      I think, you may need to modify your web.config then add "maxRequestLength" and "maxAllowedContentLength"



                      <system.web>
                      <compilation debug="true" targetFramework="4.5.2"/>
                      <httpRuntime targetFramework="4.5.2" maxRequestLength="50240" executionTimeout="600"/> <!-- in Kb -->
                      </system.web>
                      <system.webServer>
                      <security>
                      <requestFiltering>
                      <requestLimits maxAllowedContentLength="52428800" /> <!-- in byte (50 Mb) -->
                      </requestFiltering>
                      </security>





                      share|improve this answer
























                      • I already tried setting maxAllowedContentLength, it doesn't make a difference. I'm using .NET Core, so I'm not sure System.Web will work, specially referencing 4.5.2 as targetFramework.

                        – Jurjen
                        Nov 22 '18 at 11:13


















                      0














                      I think, you may need to modify your web.config then add "maxRequestLength" and "maxAllowedContentLength"



                      <system.web>
                      <compilation debug="true" targetFramework="4.5.2"/>
                      <httpRuntime targetFramework="4.5.2" maxRequestLength="50240" executionTimeout="600"/> <!-- in Kb -->
                      </system.web>
                      <system.webServer>
                      <security>
                      <requestFiltering>
                      <requestLimits maxAllowedContentLength="52428800" /> <!-- in byte (50 Mb) -->
                      </requestFiltering>
                      </security>





                      share|improve this answer
























                      • I already tried setting maxAllowedContentLength, it doesn't make a difference. I'm using .NET Core, so I'm not sure System.Web will work, specially referencing 4.5.2 as targetFramework.

                        – Jurjen
                        Nov 22 '18 at 11:13
















                      0












                      0








                      0







                      I think, you may need to modify your web.config then add "maxRequestLength" and "maxAllowedContentLength"



                      <system.web>
                      <compilation debug="true" targetFramework="4.5.2"/>
                      <httpRuntime targetFramework="4.5.2" maxRequestLength="50240" executionTimeout="600"/> <!-- in Kb -->
                      </system.web>
                      <system.webServer>
                      <security>
                      <requestFiltering>
                      <requestLimits maxAllowedContentLength="52428800" /> <!-- in byte (50 Mb) -->
                      </requestFiltering>
                      </security>





                      share|improve this answer













                      I think, you may need to modify your web.config then add "maxRequestLength" and "maxAllowedContentLength"



                      <system.web>
                      <compilation debug="true" targetFramework="4.5.2"/>
                      <httpRuntime targetFramework="4.5.2" maxRequestLength="50240" executionTimeout="600"/> <!-- in Kb -->
                      </system.web>
                      <system.webServer>
                      <security>
                      <requestFiltering>
                      <requestLimits maxAllowedContentLength="52428800" /> <!-- in byte (50 Mb) -->
                      </requestFiltering>
                      </security>






                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Nov 22 '18 at 10:33









                      LemonsLemons

                      52110




                      52110













                      • I already tried setting maxAllowedContentLength, it doesn't make a difference. I'm using .NET Core, so I'm not sure System.Web will work, specially referencing 4.5.2 as targetFramework.

                        – Jurjen
                        Nov 22 '18 at 11:13





















                      • I already tried setting maxAllowedContentLength, it doesn't make a difference. I'm using .NET Core, so I'm not sure System.Web will work, specially referencing 4.5.2 as targetFramework.

                        – Jurjen
                        Nov 22 '18 at 11:13



















                      I already tried setting maxAllowedContentLength, it doesn't make a difference. I'm using .NET Core, so I'm not sure System.Web will work, specially referencing 4.5.2 as targetFramework.

                      – Jurjen
                      Nov 22 '18 at 11:13







                      I already tried setting maxAllowedContentLength, it doesn't make a difference. I'm using .NET Core, so I'm not sure System.Web will work, specially referencing 4.5.2 as targetFramework.

                      – Jurjen
                      Nov 22 '18 at 11:13













                      0














                      Default limit size 65 KB in WCF. Could you try to add below field inside of your binding configuration.
                      <binding maxReceivedMessageSize="10485760">






                      share|improve this answer




























                        0














                        Default limit size 65 KB in WCF. Could you try to add below field inside of your binding configuration.
                        <binding maxReceivedMessageSize="10485760">






                        share|improve this answer


























                          0












                          0








                          0







                          Default limit size 65 KB in WCF. Could you try to add below field inside of your binding configuration.
                          <binding maxReceivedMessageSize="10485760">






                          share|improve this answer













                          Default limit size 65 KB in WCF. Could you try to add below field inside of your binding configuration.
                          <binding maxReceivedMessageSize="10485760">







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Nov 22 '18 at 10:37









                          Mustafa TığMustafa Tığ

                          589




                          589






























                              draft saved

                              draft discarded




















































                              Thanks for contributing an answer to Stack Overflow!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53428474%2fresponse-413-request-entity-too-large%23new-answer', 'question_page');
                              }
                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              Guess what letter conforming each word

                              Port of Spain

                              Run scheduled task as local user group (not BUILTIN)