URL wildcard condition

Warning: As of Chromium 52, the full URLs of the https:// scheme are no longer provided to PAC scripts. As a result, URL wildcard and URL regex conditions may not work properly in SwitchyOmega.

When matching the host name is not sufficient, wildcard matching can be performed on the whole URL.

For matching entire sites, use host wildcard conditions. For keyword matching on HTTP only, use keyword conditions. The two new types of conditions should replace most usage of URL wildcard conditions.

Example

Pattern: http://www.example.com/*

Matching: http://www.example.com/home, http://www.example.com/?q=test

Not matching: https://www.example.com/home, https://www.example.com.test/

Use cases

Matching URL with ports

The URL wildcard condition type allows matching the full URL, enabling port-based conditions. For example,

• PORT 1935: *://*:1935/*
• PORT 45591: *://*:45591/*
• All HTTPS URLs: https://*
  • The HTTPS protocol defaults to port 443. In that case the port number is not present in the URL string.

Design goals

URL wildcard conditions are not so popular as host wildcard conditons. But this is not a reason for not optimizing them.

Wildcard optimization should be used for simple wildcards on compiling, whenever possible.

Most URL wildcards will only include *s at the beginning, the end, or both. Focus on translating them to string functions for greater speed.

If optimization is not possible, they should be translated to regexes on PAC generation. shExpMatch calls new RegExp internally in Chromium, so this function should not be used at all.