-
Notifications
You must be signed in to change notification settings - Fork 96
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
bisonw-desktop: don't force tls for mac os desktop app #2923
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -667,7 +667,11 @@ func (s *WebServer) Connect(ctx context.Context) (*sync.WaitGroup, error) { | |
// Safari. When this is removed, the allowInCSP variable can be removed | ||
// but prepareAddr should still return 127.0.0.1 for unspecified | ||
// addresses. | ||
s.csp = fmt.Sprintf("%s ws://%s", baseCSP, addr) | ||
scheme := "ws" | ||
if s.srv.TLSConfig != nil { | ||
scheme = "wss" | ||
} | ||
s.csp = fmt.Sprintf("%s %s://%s", baseCSP, scheme, addr) | ||
Comment on lines
-670
to
+674
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is where I encountered a problem on an older version of MacOS (v12 Monterey). We were forcing TLS, so the websocket scheme was |
||
} | ||
s.addr = addr | ||
|
||
|
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure why this setting would be forced. I do see there was a tangentially related comment in the PR, and I'm wondering if it was misinterpreted. Hopefully @ukane-philemon can shed some light, but I don't see a reason to default to TLS on the desktop app, which will always be running localhost.