ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-22 04:35:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'clio_forwarding_rules'

Browse Source
This commit is contained in:
mDuo13
2023-10-16 16:38:10 -07:00
parent 5ec8f96a67 fd88037351
commit 970e7e3e6a
2 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
content/concepts/networks-and-servers/the-clio-server.md
View File

@@ -36,6 +36,12 @@ A Clio server stores validated ledger data such as transaction metadata, account
When a Clio server receives an API request, it looks up data from these data stores. For requests that require data from the P2P network, the Clio server forwards the request to a P2P server, and then passes the response back to the client. When a Clio server receives an API request, it looks up data from these data stores. For requests that require data from the P2P network, the Clio server forwards the request to a P2P server, and then passes the response back to the client.
Clio will **always** forward to `rippled` if any of the following is true:
- `ledger_index` is set to `current` or `closed`.
- `accounts`, `queue` or `full` are set to `true` for the `ledger` API.
- `queue` is set to `true` for the `account_info` API.
- Requested API method (`"command"`) is `submit`, `submit_multisigned`, `fee`, `ledger_closed`, `ledger_current`, `ripple_path_find`, `manifest`, `channel_authorize` or `channel_verify`.
## See Also ## See Also

1
dactyl-config.yml
View File

@@ -842,6 +842,7 @@ pages:
- en - en
- md: "@i18n/ja/concepts/networks-and-servers/the-clio-server.md" - md: "@i18n/ja/concepts/networks-and-servers/the-clio-server.md"
outdated_translation: true
targets: targets:
- ja - ja