Repository navigation
Respond locally to Bedrock Xbox status pings - #811
Open
guhlutions wants to merge 1 commit into
Open
guhlutions wants to merge 1 commit into
guhlutions wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A Java server-list query to a Bedrock Realm sends its Xbox signaling session ID to the dedicated-server HTTP status lookup. The lookup tries to resolve that ID as a hostname and fails with
UnknownHostException.For Xbox and Xbox JSON-RPC signaling addresses, reply to the Java status request locally and echo the client's timestamp in the pong. Use the client's protocol and the configured MOTD when present. The displayed latency is the round trip to ViaProxy. Dedicated Bedrock servers continue to use their HTTP status endpoint.
Verified the status response and matching pong for both Xbox address types with Java 26.3 and 1.21.4. Also tested a custom MOTD and player counts from a dedicated server's HTTP status endpoint. Reproduced the original error with the previous build and verified the new response against a running Realm-configured proxy.