reqWrite

Saves the request body to a specified directory or file. Suitable for scenarios where request data needs to be recorded:

• Automatically generates a file path based on the request URL
• Uses a safe write policy (can be forced to overwrite using enable://forceReqWrite)
• Only valid for requests with a body (POST/PUT/PATCH, etc.)
• Automatically skips requests without a body, such as GET/HEAD
• Automatically skips if saving fails

Rule Syntax

pattern reqWrite://fileOrDirPath [filters...]

Configuration Example

Basic Configuration

wproxy.org/docs reqWrite:///User/xxx/test/

Path Resolution Rules:

1. When Accessing a Specific File

   https://wproxy.org/docs/test.html

   → Save to: /User/xxx/test/test.html

2. When Accessing a Directory Path

   https://wproxy.org/docs/

   → Save to: /User/xxx/test/index.html (The target path is /User/xxx/test/, and a trailing / or \ automatically appends index.html)

Explicit Directory Configuration

wproxy.org/docs/ reqWrite:///User/xxx/test/

Path Resolution Differences:

1. When Accessing a Sub-Path

   https://wproxy.org/docs/test.html

   → Still Saved to: /User/xxx/test/test.html

2. When Accessing a Configuration Directory

   https://wproxy.org/docs/

   → Saved Directly to: /User/xxx/test/ (as a Whole File)

💡 Key Differences:

• Whether the rule path ends with / or \ determines how directory requests are saved
• Non-directory paths (without a trailing / or \) are saved directly to the specified file
• Directory paths (with a trailing / or \) are automatically completed to index.html

Specified Files

/^https://wproxy\.org/docs/(\?.*)?$ reqWrite:///User/xxx/test/index.html

Limit the request URL using regular expression matching

Associated Protocols

1. Enable force write: enable://forceReqWrite
2. Write all request contents: reqWriteRaw