Skip to content

reqHeaders

Dynamically modify request header information, supporting multiple data sources and batch operations.

Rule Syntax

txt
pattern reqHeaders://value [filters...]
ParametersDescriptionDetailed Documentation
patternExpression to match request URLsMatch Pattern Documentation
valueOperation data object, supported from the following channels:
• Directory/file path
• Remote URL
• Inline/embedded/Values content
Operation Instruction Documentation
filtersOptional filters, supported for matching:
• Request URL/method/header/content
• Response status code/header
Filter Documentation

Configuration Example

Basic Configuration

txt
www.example.com/path reqHeaders://x-proxy=Whistle

Access https://www.example.com/path/to You can see the new request headers on Whistle Network or the backend server:

txt
x-proxy: Whistle

Setting Multiple Request Headers

txt
``` test.json
x-test1: 1
x-test2:
x-test3: abc
```
www.example.com/path2 reqHeaders://{test.json}

# Equivalent to: www.example.com/path2 reqHeaders://x-test1=1&x-test2=&x-test3=abc

Visiting https://www.example.com/path2/to You can see the new request headers on Whistle Network or the backend server:

txt
x-test1: 1
x-test2:
x-test3: abc

Local/Remote Resources

txt
www.example.com/path1 reqHeaders:///User/xxx/test.json
www.example.com/path2 reqHeaders://https://www.xxx.com/xxx/params.json
# Editing a temporary file
www.example.com/path3 reqHeaders://temp/blank.json
  1. More flexible way to modify request headers: headerReplace
  2. Deleting request header fields: delete://reqHeaders.xxx