You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -431,6 +431,7 @@ Supported proxy schemes are:
431
431
*`force-resolve` - pseudo-proxy forcing domain name resolve before it will be passed to the next proxy in the chain. Must wrap actual proxy dialer in the chain (i.e. be specified in last `-proxy` argument). Example: `force-resolve://`
432
432
*`chain` - pseudo-proxy assembling a chain from other proxy specifications. Query string parameters are:
433
433
*`next` - specification of the next proxy in chain. This query string parameter can be specified more than once. Example: `chain://?next=http%3A%2F%2F127.0.0.1%3A57800&next=force-resolve%3A%2F%2F`.
434
+
*`set-dst` - pseudo-proxy replacing connection destination address with the one specified in hostname part of URI. It is mostly intended for programmatic usage from within routing JS script. Example: `set-dst://localhost:9999`.
0 commit comments