anchor.diff:      <td>AttemptedTLSWith<br/>NonTLSBackend</td>
       <td>525</td>
       <td>Yes</td>
  -    <td>Platform*</td>
  +    <td>Platform</td>
       <td>Logs with error <code>tls: first record does not look like a TLS handshake</code> or <code>backend_tls_handshake_failed</code> metric increments</td>
     </tr>
     <tr>
  
positive.code:     <td> 502</td>
      <td> Yes</td>
      <td> Platform</td>
      <td> Logs error <code>x509: certificate has expired or is not yet valid</code>.
           This error can occur if the Diego Cell clock drifts.</td>
    </tr> 
  </table>  
  
  &#42; Any platform issue could be the result of a misconfiguration.</p>
  
  ## <a id="app-errors"></a>Diagnose App Errors
  
  
negative.code: 
  ## <a id="gorouter-error-classification"></a> Gorouter Error Classification Table
  
  Use this table when you are debugging Gorouter errors.
  The table lists error types, status codes, and indicates if the Gorouter retries the errored request.
  
  For each error, there is a `backend-endpoint-failure` log entry in `gorouter.log`
  and an error message in `gorouter.err.log`.
  Additionally, the `access.log` records the request status codes.
  For more information, see the [Gorouter documentation](https://github.com/cloudfoundry/gorouter#logs) on GitHub.
  
  If the request is one that can be retried, Gorouter makes up to three attempts.
  
  <table class="nice">
    <th width="15%">Error Type</th>
  