Skip to content
This repository has been archived by the owner on Mar 1, 2024. It is now read-only.

Fixing matchmaker directing users to http when the signalling server is using https #245

Merged
merged 1 commit into from
Jun 6, 2023
Merged

Conversation

mcottontensor
Copy link
Contributor

@mcottontensor mcottontensor commented Jun 6, 2023

Relevant components:

  • Signalling server
  • Frontend library
  • Frontend UI library
  • Matchmaker
  • Platform scripts
  • SFU

Problem statement:

When the signalling server is configured to use HTTPS the matchmaker would still direct the users to the HTTP port. See #207

Solution

When the signalling server starts and communicates with the matchmaker it now supplies the correct HTTP or HTTPS port based on config.UseHTTPS allowing the matchmaker to redirect users to the correct port.

Test Plan and Compatibility

Run the matchmaker with or without HTTPS and attempt running the signalling server with and without UseHTTPS configurations. Make sure that the matchmaker directs the user to the correct port and the streaming application runs as expected.

@mcottontensor mcottontensor requested a review from lukehb June 6, 2023 04:07
Copy link
Contributor

@lukehb lukehb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved.

@lukehb lukehb linked an issue Jun 6, 2023 that may be closed by this pull request
@lukehb lukehb merged commit 556d501 into EpicGames:master Jun 6, 2023
@mcottontensor mcottontensor deleted the gh207 branch June 14, 2023 03:40
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] - Matchmaker Redirecting Player to HTTP port when UseHTTP is true
2 participants