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

Possible websockets blocking issue #586

Closed
vozersky opened this issue Mar 10, 2017 · 11 comments
Closed

Possible websockets blocking issue #586

vozersky opened this issue Mar 10, 2017 · 11 comments
Assignees
Milestone

Comments

@vozersky
Copy link
Member

vozersky commented Mar 10, 2017

Test fails in Safari

@vozersky vozersky added this to the 2.6.0 Beta milestone Mar 10, 2017
@atropnikov
Copy link
Member

@vozersky Which test did fail? I cannot reproduce it.

@atropnikov atropnikov self-assigned this Mar 14, 2017
@vozersky
Copy link
Member Author

@atropnikov the one I mentioned in the first post (2. Test blocking simple websocket connection)

@vozersky vozersky reopened this Mar 30, 2017
@atropnikov atropnikov modified the milestones: 2.6, 2.6.0 Beta Mar 30, 2017
@vozersky vozersky added the Safari label Apr 4, 2017
@ameshkov
Copy link
Member

ameshkov commented Apr 4, 2017

What's exact Safari version?

It was fixed a long time ago:
#299

@vozersky
Copy link
Member Author

vozersky commented Apr 5, 2017

@ameshkov Version 10.1 (12603.1.30.0.34)

@ameshkov
Copy link
Member

ameshkov commented Apr 5, 2017

We might need to fix the test code. @atropnikov please assist.

@atropnikov
Copy link
Member

@ameshkov What do you mean? Check the version of Safari in tests, or something else?

@ameshkov
Copy link
Member

ameshkov commented Apr 6, 2017

First of all we should figure out why test fails. Could it be that WebSocket does not throw error or something like that?

@atropnikov
Copy link
Member

I found a reason of the problem. Test filter contains ||echo.websocket.org/?blocked rule.
We replace || with var URL_FILTER_REGEXP_START_URL = "^https?://([^/]*\\.)?";
That's why WS connection isn't blocked.

@ameshkov
Copy link
Member

ameshkov commented Apr 6, 2017

@atropnikov we should've resolved it long ago, || should cover WebSocket as well. However, it'd be better to leave regexp pattern relatively simple.

@ameshkov
Copy link
Member

ameshkov commented Apr 6, 2017

I wonder, what will be the difference in performance?
^(http|ws)s?

@atropnikov
Copy link
Member

Safari doesn't support |

atropnikov added a commit that referenced this issue Apr 6, 2017
adguard pushed a commit that referenced this issue Mar 6, 2020
…AG-1126 to master

* commit 'bd256c06e635e498cd307f6694b0afcc1a75b626':
  AG-1126 add example of working rule in test
  AG-1126 ignore rules with length less than 4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants