title: WebApi only accepting 4079 characters in POST body
body: <p>I'm developing an Ionic 3 mobile application and using ASP.NET REST WebAPI 2 as my back-end.</p>
  
  <p>I've been trying to pass a base64 string ( around 150kb big enocoded png image) to one of my webAPI methods without any success for the last couple of days.</p>
  
  <p><a href="https://i.stack.imgur.com/GrSt5.png" rel="nofollow noreferrer">My API call</a></p>
  
  <p><a href="https://i.stack.imgur.com/is7tz.png" rel="nofollow noreferrer">Method that I'm calling in my WebAPI</a></p>
  
  <p>The problem is that the WebApi doesn't seem to receive any values, as seen 
  <a href="https://i.stack.imgur.com/qn6El.png" rel="nofollow noreferrer">HERE</a></p>
  
  <p>I'm sending my data with these <a href="https://i.stack.imgur.com/xFuiV.png" rel="nofollow noreferrer">HEADERS</a></p>
  
  <p>Upon further inspection I noticed the following. I intercepted the api call with Postman and discovered that the webApi receives data, but cuts the data at 4079th character as seen <a href="https://i.stack.imgur.com/7jAAm.png" rel="nofollow noreferrer">HERE</a>. Since the webAPI seems to cut the JSON string at 4079th character, the JSON itself isn't complete which (I'm guessing) is the reason why the webAPI can't read it and also why the values are all empty while debugging the webAPI method in Visual Studio.</p>
  
  <p>Here is another interesting thing. In Chrome Development tools under the Network section I can see the API call with all the additional info. Chrome also shows the FULL base64 string as seen <a href="https://i.stack.imgur.com/rlzZ7.png" rel="nofollow noreferrer">HERE</a>.</p>
  
  <p>Does anyone have any idea what's going on here? Has anyone else experienced similar problems before?</p>
  
  <p>UPDATE 1: </p>
  
  <p>I just added <a href="https://i.stack.imgur.com/T3yET.png" rel="nofollow noreferrer">THIS</a> to my Web.config as @evayly suggested.</p>
  
  <p>I also tried adjusting the following values:</p>
  
  <p>maxAllowedContentLength</p>
  
  <p>maxRequestLength</p>
  
  <p>aspnet:MaxJsonDeserializerMembers </p>
  
  <p>but it didn't solve the problem.</p>
  
  <p>UPDATE 2</p>
  
  <p>Another part of interesting info:</p>
  
  <p>If I manually edit the intercepted post in Postman by adding json closing tags - " }   and resend it, the method reads  the data without any problems. So i think the main problem is something cutting my json to 4079 characters --> creating a json string without the proper closing tags and thus making my json invalid.</p>