If you are not familiar with Clash Meta and Fiddler Everywhere, follow the link to learn about them before reading this post.
Basic Thought
- Fiddler Everywhere provide HTTP proxy endpoint
- Clash Meta allow adding HTTP proxy as proxy node
Then we have the following thought:
---
config:
theme: default
---
flowchart TB
n4["System Traffics"]
n4["System Traffics"] --catch all traffic--> A
n1["Rule Engine"]
A["Clash Core<br>(TUN Enabled)"] --> n1["Rule Engine"]
n1 --not from fiddler--> n2["Fiddler<br>HTTP proxy endpoint"]
n1 --from fiddler--> n3["Internet"]
n2 -- outgoing data has been treated as general system traffic again --> n4
n4@{ shape: rect}Rule Settings
First create an HTTP proxy node pointing to Fiddler Everywhere HTTP proxy:
prepend:
- name: 'Fiddler'
type: 'http'
server: '127.0.0.1'
port: 34567
Based on previous settings, the actual config should be:
prepend:
- 'PROCESS-NAME,Fiddler.WebUi.exe,🚀 节点选择'
- 'PROCESS-NAME,Fiddler Everywhere.exe,🚀 节点选择'
- 'MATCH,Fiddler'
Note that Clash Verge do not allow to choose proxy node like “Fiddler” directly in the UI, you may need to manually enter the node name in advanced edit mode.