Header Editor

Rule

Rule

Match type

Rules will apply to the URL that meets the matching criteria. If multiple conditions are checked, all conditions must be met at the same time for this rule to be applied.

  • All: Correspond to all urls, including the Header Editor itself
  • Regular expression
    • Supports standard JS regular expressions. For example, the regular expression you entered is str, then, in fact, the program will use the internal new RegExp(str) to initialize the regular expression.
    • If the match rule is a regular expression, the modification result (currently including redirect to) supports the use placeholder like $1
    • Learn more about regular expression on Mozilla Developer Network
  • URL prefix: Including http:// URL prefix
  • Domain name: The full domain name that contains the subdomain
  • URL: Including "?" And the full address of all subsequent content
  • Method: GET/POST and other request methods.
  • Resource type: web page, image, CSS style, etc.

Note:

  • The method and resource type can only be configured in either match or exclude.

Exclude

Regardless of whether the matching rules are met, as long as any exclusion condition is met, this item will not take effect on the current URL.

  • The Lite version does not support configuring regular expressions in exclusion.

Custom function

Through a custom function to realize a more flexible function, the specific use please see here

  • This feature is not supported in the Lite version.

Other special features

  • When using "Modify request header" or "Modify response header", set the header content to _header_editor_remove_ will remove this header (valid since 3.0.5)
  • When using "Redirect request" with custom function, return _header_editor_cancel_ will cancel this request (valid since 4.0.3)

Other considerations

  • If you want to set a header content to empty, different browsers have different behaviors. Chrome will keep this header but its content will be empty. Firefox will remove this header
  • Browsers restrict modification of specific URLs. For example, in Chrome and similar browsers (such as 360 Browser), extensions do not have permission to modify any request starting with chrome.google.com/webstore.

A common feature example

The following example is not guaranteed to be valid, only as an example to help users familiarize themselves with the rules of the Header Editor

Redirect requests

For example, the Google public library is redirected to the mirror image of University of Science and Technology of China:

Regular expressions is ^http(s?)://(ajax|fonts)\.googleapis\.com/(.*), redirect to https://$2.proxy.ustclug.org/$3

Redirect all HTTP requests of sale.jd.com, item.jd.com and www.jd.com to the HTTPS:

Regular expressions is http://(sale|item|www).jd.com, redirect to https://$1.jd.com

Redirect all wikipedia's HTTP requests to HTTPS:

Regular expressions is ^http://([^\/]+\.wikipedia\.org/.+), redirect to https://$1

Camouflage UA

Just modify the request header named User-Agent, but the function can only affect the ability of the server to determine UA, which can not be pseudo in local through JS

ON THIS PAGE