-
Notifications
You must be signed in to change notification settings - Fork 123
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
Rules from subscriptions won't match URL contains port #304
Comments
Can you provide such list here? |
My Rule and an example douyu live streaming. |
these rules you mean?
These are defined for default port 80 and 443 because port is not mentioned in them.
|
That is because of the table plugin, nothing I can do about it, clean the table constantly to keep the flow going |
But both gfwlist syntax and ABP filters mentions no port, I believe ALL Port should be included even not announced with the single rule of |
The implementation of SwitchyOmega rules and AutoProxy rules are imported from their libraries so we have currently what they have ! Same logic |
I have not written the rules parser code, so it must some misunderstanding between deployments! SwitchyOmega is not working in Chrome anymore, are you using something custom ? |
No, I'm on official Google Chrome v114.0.5735.199. |
I found that this issue is caused by the fix for #298 I'm putting a release to patch this. Thanks for the report |
I mean are you using custom version of SwitchyOmega? it is not working for me |
I think I'm using the official one. |
Verion 1.2.1 is release to Chrome, you can check if it is working fine. |
Same issue. 1.2.1 is still not working. |
The issue is fixed, but the fix is not applied to Proxyable Resources page, in Chrome browsers this page can't use same engine as the Proxy engine. Its browser limitations. |
Confirmed from my proxy log that all port related issues on rule seem to have been fixed. |
Description
won't match
wss://wsproxy.douyu.com:6675/
Steps to Reproduce
Which browsers did you test this on?
Chrome
Affected browser versions
Chrome 114
Affected SmartProxy versions
SmarProxy 1.2.0
Screenshots of the problems or steps to reproduce
No response
Any additional context
I find #238 in the issues.
The same thing happens to
DomainSubdomain
though I can change toHost regex
there.You can't do that with Rules Subscriptions
The text was updated successfully, but these errors were encountered: