docs: reverse proxy feature #605
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR updates the documentation for the reverse proxy feature by deprecating the legacy article in the knowledge-base and introducing a new, consolidated guide in the capture-traffic section.
- Removed the outdated "Fiddler as Reverse Proxy" article from the knowledge-base.
- Added a new and comprehensive "Reverse Proxy" guide in the capture-traffic section.
- Updated the capturing-modes documentation to include reverse proxy support.
Reviewed Changes
Copilot reviewed 3 out of 9 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| knowledge-base/fiddler-as-reverse-proxy.md | Removed legacy documentation for Fiddler reverse proxy configuration. |
| capture-traffic/reverse-proxy.md | Added a detailed guide for setting up and using Fiddler's reverse proxy mode. |
| capture-traffic/capturing-modes.md | Updated table and added a new section to document reverse proxy capturing mode. |
There was a problem hiding this comment.
Reverse proxy is most useful if you want to keep your client unchanged and instead use Fiddler to replace the server. In the example you modify the client, which is still valid, but not what customers want when they need a reverse proxy - modifying the client is also done when using fiddler as a normally - to proxy the requests to the server.
I think that the example should be changed so the client remains the same and the server port is changed so Fiddler Everywhere can start listening on the original server port.
In addition, I don't see a need to show the rules based method now that we have an easier and cleaner way to do it. Perhaps it can be replaced with another example - e.g. showing how to use the hosts file and create a reverse proxy for a internet web server.
- edit your hosts file and add "127.0.0.1 www.example.com"
- add a reverse proxy rule in fiddler on client port 443 (explain that fiddler might need to be run as administrator for ports<1024), client protocol https, remote host 212.95.165.25 (explain how to find the IP of www.example.com), remote protocol https, preserve host true
- make a request in the browser for https://www.example.com and see it captured in Fiddler without using system proxy or network capture.
|
Lini's comments make sense. Since the reverse proxy is a server-side proxy better change the server port and not the client. |
There was a problem hiding this comment.
for the remote example - I think you need to add two more points:
- if you want to capture ports <1024 - e.g. you want to mimic https://www.example.com/ on port 443, you need to run FE as administrator
- if you are using a remote IP address to mimic the www.example.com site, you need to make sure ignore server errors is ON, otherwise there will be a certificate error when Fiddler tries to connect to the IP if its a cloud server and hosts more than one web application. Furthermore the Preserve host header option MUST be on when you are redirecting to an IP address because otherwise FE does not know which web site you are trying to reach.
related to https://kinvey.atlassian.net/browse/FID-7510