title: MaxExpansionDepth with latest webapi and breeze
body: <p>I have recently updated all of my nuget packages to the latest for EF6, breeze 1.4.5, system.web.http.odata 5.0.0.0, and all the other good bits available.</p>
  
  <p>Now, with one query that contains an expansion like x.y.z I get an error as follows:</p>
  
  <pre><code>A first chance exception of type 'Microsoft.Data.OData.ODataException' occurred in System.Web.Http.OData.dll
  
  Additional information: The request includes a $expand path which is too deep. The maximum depth allowed is 2. To increase the limit, set the 'MaxExpansionDepth' property on QueryableAttribute or ODataValidationSettings.
  </code></pre>
  
  <p>I looked into the suggested fixes.  If I add a Queryable attribute on the breeze 'endpoint' being queried, it appears to cause all sorts of other problems.  My guess is it interferes with breeze's expected behaviour and formats the results differently.</p>
  
  <p>I then looked into the using the HttpConfiguration EnableQuerySupport extension method, through GlobalConfiguration.Configuration..., but that appears to have no effect (see <a href="http://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/supporting-odata-query-options">Supporting OData Query Options</a>)</p>
  
  <p>Does anybody have any idea how I can change the default webapi behaviour?</p>
  
  <p>Thanks.</p>