Match snikket-server default for internal http#29
Open
Zash wants to merge 1 commit into
Open
Conversation
Snikket-Server currently defaults to 127.0.0.1, without ::1. The proxy defaulting to 'localhost' means it has to resolve that name, which would give it both 127.0.0.1 and ::1 in many environments from this century. That lookup and failed attempt to connect to ::1 adds latency and errors to the log. Example error: [error] 16#16: *1 connect() failed (111: Connection refused) while connecting to upstream, client: ::1, server: chat.example.org, request: "GET /login HTTP/1.1", upstream: "http://[::1]:5765/login", host: "chat.example.org" Some alternative ways this could be fixed: - Somehow support specifying multiple interfaces. - Add a way to mark a service as 'private' in Prosody
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.
Snikket-Server currently defaults to 127.0.0.1, without ::1.
The proxy defaulting to 'localhost' means it has to resolve that name, which would give it both 127.0.0.1 and ::1 in many environments from this century. That lookup and failed attempt to connect to ::1 adds latency and errors to the log.
Example error:
Some alternative ways this could be fixed: