Skip to content

[Bug]: field starting with wildcard doesn't work properly #139

Description

@rasoolZero

Platform

Windows

ProxyBridge Version

3.2.0

OS and Version

Windows 10

Documentation

Code Review

  • I have gone through the code page

Describe the Bug

  1. Go to Proxy Rules
  2. Add a rule with Application starting with wildcard, in my scenario: *steam*
  3. Rule doesn't work properly, instances of steam and its sub-processes (e.g. steam.exe or steamwebhelper.exe ) connect DIRECTly by default.

Expected behavior:
starting wildcard should mean anywhere in the string, which in this case is not working.

Additional Context

No response

Metadata

Metadata

Assignees

Labels

Type

No fields configured for Bug.

Projects

Status
In review

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions