---
schema_version: "1"
id: f8668fd966622f6a58e95f30ff805b75df6cce5f503329cdad45a5ea5d5f8d07
title: Handling API Proxy Status Codes
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/api-manager/latest/wsdl-raml-http-proxy-reference.md
canonical_url: https://docs.mulesoft.com/api-manager/latest/wsdl-raml-http-proxy-reference
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 73e343316a58a8e254efd0cbc49035b7476ae8a3feb4f13f10ddfa91baa28a4f
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: API Manager
version: 2.x
is-latest-version: true
---

# Handling API Proxy Status Codes

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

In Mule 4, WSDL, RAML, HTTP, and HTTPS proxies handle errors and requests as described in the
following tables. Mule 4 returns different error codes, depending on the proxy type, or no error
code in response to problematic requests. This table shows whether or not Mule returns a 504, 400,
or 404 error code when your WSDL, RAML, HTTP, and HTTPS proxy receives a problematic request.

<table><colgroup><col> <col> <col> <col> <col> <col></colgroup><thead><tr><th>Error Code</th><th>WSDL</th><th>RAML</th><th>OAS</th><th>HTTP</th><th>HTTPS</th></tr></thead><tbody><tr><td><p>504: request timeout</p></td><td><p>yes</p></td><td><p>yes</p></td><td><p>yes</p></td><td><p>yes</p></td><td><p>yes</p></td></tr><tr><td><p>400: bad request (validation result)</p></td><td><p>yes</p></td><td><p>no</p></td><td><p>yes</p></td><td><p>no</p></td><td><p>no</p></td></tr><tr><td><p>404: resource not found</p></td><td><p>no</p></td><td><p>yes</p></td><td><p>yes</p></td><td><p>no</p></td><td><p>no</p></td></tr><tr><td><p>405: method not allowed in API spec</p></td><td><p>no</p></td><td><p>no</p></td><td><p>yes</p></td><td><p>no</p></td><td><p>no</p></td></tr></tbody></table>