title: HTTP 500 – Wordpress WP-API without any message?
body: <p>I'm using <a href="http://framework.themosis.com/" rel="nofollow">themosis</a> – a framework for wordpress that works pretty well. Also I use <a href="https://github.com/WP-API/WP-API" rel="nofollow">WP-API</a> - that doesn't work so great.</p>
  
  <p>All versions are the latest stables and the Server is using PHP 5.5</p>
  
  <p>On calling that API route:</p>
  
  <pre><code>posts?filter[order]=ASC&amp;filter[orderby]=name&amp;filter[posts_per_page]=-1&amp;type=products
  </code></pre>
  
  <p>I'm getting an Internal Server error / HTTP 500</p>
  
  <blockquote>
    <h1>Internal Server Error</h1>
    
    <p>The server encountered an internal error or misconfiguration and was
    unable to complete your request.</p>
    
    <p>Please contact the server administrator, webmaster@example.ch and
    inform them of the time the error occurred, and anything you might
    have done that may have caused the error.</p>
    
    <p>More information about this error may be available in the server error
    log.</p>
  </blockquote>
  
  <p>So my hoster checked the logs and the only lines caused by this error were:</p>
  
  <pre><code>[Tue Jul 07 17:43:13 2015] [error] Premature end of script headers: php55-fcgi-starter.fcgi, referer: {myurl/mypath}
  </code></pre>
  
  <p>I checked all log, forced everything to display errors &amp; logs, but no PHP errors - not even notices... (set <code>display_errors</code> to <code>On</code> and <code>error_reporting</code> to <code>2039</code> - with htaccess and php-side (wordpress index.php)</p>
  
  <hr>
  
  <p>I just figured out that when I set the <code>post_per_page</code> filter is set to e.g. 90 it works, but only till a specific post.</p>
  
  <p>All posts are "normal" - making a <code>WP_Query</code> also delivers all results without any issues.</p>
  
  <hr>
  
  <p>I also increased the php memory_limit to more than enough and tested it locally (Mac OS / MAMP) what works great.</p>
  
  <p>I really can't find any reason why this is happening. My server hoster support (which is really good actually) says also that all systems run fine</p>