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.

Sign up for GitHub

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

Jump to bottom

[Chrome] Sites using custom port are not detected by Smart rules. #298

Closed
Nyar233 opened this issue Jul 4, 2023 · 3 comments
Closed

[Chrome] Sites using custom port are not detected by Smart rules. #298

Nyar233 opened this issue Jul 4, 2023 · 3 comments
Labels
type-bug Bug in code or behaviour

Comments

@Nyar233
Copy link

Nyar233 commented Jul 4, 2023

Describe the bug

The plugin seems to be unable to proxy websites that use non-standard ports like https://example.com:2345

This issue is observed on Chrome browser

To Reproduce
Open the extension menu, then check the websites that need to be proxied under “Manually enable proxy”, then refresh

Expected behavior
The website should be proxied normally

SmartProxy (please complete the following information):

  • Version: 1.1.1

Browser (please complete the following information):

  • Browser Chrome
  • Version 114.0.5735.199

Additional context
If you use this extension on Firefox browser, it seems to work fine
@salarcode salarcode changed the title （Chrome）When using auto-switch, the plugin cannot proxy properly on websites that use non-standard ports [Chrome] Sites using custom port are not detected by Smart rules. Jul 9, 2023
@salarcode salarcode added the type-bug Bug in code or behaviour label Jul 9, 2023
@salarcode
Copy link
Owner

Thanks for the report, the issue is very bizarre and should not have happened or maybe it is happened after version 1.0

The issue is fixed and will be out with next release

salarcode added a commit that referenced this issue Jul 16, 2023
@salarcode
Correcting fix for Chrome 'FindProxyForURL' doesn't include port number
a8018ea 
Closes #298, Closes #304
@salarcode salarcode mentioned this issue Jul 16, 2023
Closed
@Nyar233
Copy link
Author

Nyar233 commented Jul 19, 2023 •
edited
Loading

After updating smartproxy to 1.3.0, the problem reappears.

@salarcode

salarcode added a commit that referenced this issue Jul 19, 2023
@salarcode
Regression fix in [Chrome] sites using custom port are not detected b…
b22e7a6 
…y Smart rules. #298
@salarcode
Copy link
Owner

Yeah that`s a regression, will be fixed by 1.3.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type-bug Bug in code or behaviour
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@salarcode @Nyar233