Interface ProxyFailure

All Known Implementing Classes:
ProxyFailure.BadRequest, ProxyFailure.BadServerResponse, ProxyFailure.ConnectFailed, ProxyFailure.NoConnectionAvailable, ProxyFailure.NoRoute, ProxyFailure.RequestTooLarge, ProxyFailure.ServerTimeout, ProxyFailure.TlsFailed, ProxyFailure.UnresolvedHost

Why the proxy has to answer a request itself instead of relaying the server's response. Each failure knows the status of the proxy's default answer; HttpFilters.proxyToServerFailure(org.microproxy.ProxyFailure) and a FailureResponder can answer differently.

The default answers are short plain-text bodies (Bad Gateway, Gateway Timeout, ...) that never echo the request. Requests the proxy cannot parse at all (malformed or oversized heads, bad chunk framing) are answered with a plain 4xx without consulting filters or the responder, since there is no request to hand over.

  • Method Details

    • status

      Returns the status of the proxy's default answer.
      Returns:
      the status of the proxy's default answer