Skip to content

Redirect rules with websocket excluded (~websocket) are marked as invalid #3835

@Yuki2718

Description

@Yuki2718

Prerequisites

  • I verified that this is not a filter list issue. Report any issues with filter lists or broken website functionality in the uAssets issue tracker.
  • This is NOT a YouTube, Facebook or Twitch report. These sites MUST be reported by clicking their respective links.
  • This is not a support issue or a question. For support, questions, or help, visit /r/uBlockOrigin.
  • I performed a cursory search of the issue tracker to avoid opening a duplicate issue.
  • The issue is not present after disabling uBO in the browser.
  • I checked the documentation to understand that the issue I am reporting is not normal behavior.

I tried to reproduce the issue when...

  • uBO is the only extension.
  • uBO uses default lists and settings.
  • using a new, unmodified browser profile.

Description

Someone reported to AdGuardFilters repo that these rules in AdGuard filters are invalid on uBO

Screenshot Image

Since they have script specified, ~websocket is just redundant and thus already removed; nevertheless, I don't think they are invalid.

A specific URL where the issue occurs.

NA

Steps to Reproduce

  1. Paste ||trafmag.com/etarg-code.js$script,redirect=noop.js,important,~websocket to My filters

Expected behavior

They are treated as valid filters.

Actual behavior

Marked as invalid

uBO version

1.67.0

Browser name and version

Chrome 141.0.7390.108

Operating System and version

Windows 11

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions