Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RPC tooBusy response now has 503 HTTP status code: #4143

Merged
merged 1 commit into from
Jan 3, 2023
Merged

RPC tooBusy response now has 503 HTTP status code: #4143

merged 1 commit into from
Jan 3, 2023

Commits on Nov 29, 2022

  1. RPC tooBusy response has 503 HTTP status if "ripplerpc": "3.0": 

    Fixes XRPLF#4005

Makes it possible for internal RPC Error Codes to associate
themselves with a non-OK (200) HTTP status code.  There are
quite a number of RPC responses in addition to tooBusy that
now have non-OK HTTP status codes.

The new return HTTP return codes are only enabled by including
"ripplerpc": "3.0" or higher in the original request.
Otherwise the historical value, 200, continues to be returned.
    @scottschurr
    scottschurr committed Nov 29, 2022
    Configuration menu
    Copy the full SHA
    f08c1c1 View commit details
    Browse the repository at this point in the history