Skip to content
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

feat(firefox): migrate to protocol-based proxy implementation #3362

Merged
merged 1 commit into from
Aug 11, 2020

Conversation

aslushnikov
Copy link
Collaborator

@aslushnikov aslushnikov commented Aug 8, 2020

Migrate Firefox to the protocol-based proxy implementation.

This enables secure web proxies in firefox that are already supported by Chromium.

@pavelfeldman
Copy link
Member

Could you share why this is better than the options way? Options were easy to maintain (no juggler, no fork).

aType = 'socks';
else if (proxyServer.protocol === 'socks4:')
aType = 'socks4';
else if (proxyServer.protocol === 'https:')
Copy link
Member

Choose a reason for hiding this comment

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

Is it supported in other browsers? If no, let's update the docs.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It does work in Chromium! WebKit is all different across platforms - I haven't checked yet.

This migrates Firefox to the protocol-based proxy implementation.

Benefits:
- supports secure web proxies (already supported by Chromium)
- unlocks support for SOCKS proxies with authentication
@aslushnikov aslushnikov changed the title feat(firefox): roll Firefox to r1155 feat(firefox): migrate to protocol-based proxy implementation Aug 11, 2020
@aslushnikov aslushnikov merged commit 2db97e3 into microsoft:master Aug 11, 2020
@aslushnikov aslushnikov deleted the firefox-global-proxy branch August 11, 2020 18:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants