-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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.
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
Add info about Websocket/RPC port(s) to the /crawl endpoint #2837
Labels
Milestone
Comments
mDuo13
added
API Change
Feature Request
Used to indicate requests to add new features
labels
Aug 2, 2019
This would be nice to have. Anyone wanting to claim this issue, either assign yourself or raise your hand and I'll assign it to you :) |
drlongle
added a commit
to drlongle/rippled
that referenced
this issue
Feb 20, 2023
drlongle
added a commit
to drlongle/rippled
that referenced
this issue
Feb 20, 2023
drlongle
added a commit
to drlongle/rippled
that referenced
this issue
Feb 20, 2023
drlongle
added a commit
to drlongle/rippled
that referenced
this issue
Feb 20, 2023
drlongle
added a commit
to drlongle/rippled
that referenced
this issue
Feb 23, 2023
will be fixed by #4427 - expected in 1.12 |
intelliot
pushed a commit
that referenced
this issue
Jun 23, 2023
Enhance the /crawl endpoint by publishing WebSocket/RPC ports in the server_info response. The function processing requests to the /crawl endpoint actually calls server_info internally, so this change enables a server to advertise its WebSocket/RPC port(s) to peers via the /crawl endpoint. `grpc` and `peer` ports are included as well. The new `ports` array contains objects, each containing a `port` for the listening port (number string), and an array `protocol` listing the supported protocol(s). This allows crawlers to build a richer topology without needing to port-scan nodes. For non-admin users (including peers), the info about *admin* ports is excluded. Also increase test coverage for RPC ServerInfo. Fix #2837.
ckeshava
pushed a commit
to ckeshava/rippled
that referenced
this issue
Jul 10, 2023
Enhance the /crawl endpoint by publishing WebSocket/RPC ports in the server_info response. The function processing requests to the /crawl endpoint actually calls server_info internally, so this change enables a server to advertise its WebSocket/RPC port(s) to peers via the /crawl endpoint. `grpc` and `peer` ports are included as well. The new `ports` array contains objects, each containing a `port` for the listening port (number string), and an array `protocol` listing the supported protocol(s). This allows crawlers to build a richer topology without needing to port-scan nodes. For non-admin users (including peers), the info about *admin* ports is excluded. Also increase test coverage for RPC ServerInfo. Fix XRPLF#2837.
ckeshava
pushed a commit
to ckeshava/rippled
that referenced
this issue
Sep 22, 2023
Enhance the /crawl endpoint by publishing WebSocket/RPC ports in the server_info response. The function processing requests to the /crawl endpoint actually calls server_info internally, so this change enables a server to advertise its WebSocket/RPC port(s) to peers via the /crawl endpoint. `grpc` and `peer` ports are included as well. The new `ports` array contains objects, each containing a `port` for the listening port (number string), and an array `protocol` listing the supported protocol(s). This allows crawlers to build a richer topology without needing to port-scan nodes. For non-admin users (including peers), the info about *admin* ports is excluded. Also increase test coverage for RPC ServerInfo. Fix XRPLF#2837.
ckeshava
pushed a commit
to ckeshava/rippled
that referenced
this issue
Sep 25, 2023
Enhance the /crawl endpoint by publishing WebSocket/RPC ports in the server_info response. The function processing requests to the /crawl endpoint actually calls server_info internally, so this change enables a server to advertise its WebSocket/RPC port(s) to peers via the /crawl endpoint. `grpc` and `peer` ports are included as well. The new `ports` array contains objects, each containing a `port` for the listening port (number string), and an array `protocol` listing the supported protocol(s). This allows crawlers to build a richer topology without needing to port-scan nodes. For non-admin users (including peers), the info about *admin* ports is excluded. Also increase test coverage for RPC ServerInfo. Fix XRPLF#2837.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
As suggested in #2823, this could help in finding additional servers to use as a fallback for transaction submission for example. See also https://www.xrpchat.com/topic/30058-list-of-rippled-servers-with-wss-andor-json-rpc-servives/ for a need for this.
Currently there is no standard way to advertise these services, so the only other way to get this information would be to port-scan all reachable nodes. This is not a very friendly thing to do, having them advertise this in their /crawl endpoint is probably a better way forward.
The text was updated successfully, but these errors were encountered: