[Map Remote] #1 Basic UI and Logic

[NghiaTranUIT]

Description

It's time to implement the Map Remote features.

✅ It's okay to duplicate or subclass. Similar to what we've done for Map Local, Breakpoint and Scripting

1. Main UI

• [x] Implement and reuse the Main Table View + Logic

  

• [x] Right Menu Context

  

• [x] Make sure the logic of the menu context is working as Map Local, Breakpoint. For example, I can delete, duplicate, edit or create new Rule by using the Menu Context or Shortcut

• [x] Implement the Filter, similar to Map Local (Please note that Proxyman macOS doesn't support the Filter on Map Remote yet.)

• [x] Map Remote on Toolbar

[NghiaTranUIT]

2. Map Remote Edit screen

• [x] Implement the UI of the Map Remote Edit Screen

• [x] Reuse the Match Rule View from other Tools. Don't implement the new one.

  

• [x] After editing the Protocol, it automatically fills the port number to 443 if the port is empty and protocol = https

https://github.com/ProxymanApp/proxyman-windows-linux/assets/5878421/985bf7e7-5173-4f8d-8646-eb4bca9118ec

[NghiaTranUIT]

3. Port classes to Proxyman Windows

• [x] Port MapRemoteEntry, MapRemoteService and URLEntryComponent classes. Ping @NghiaTranUIT to get these file
• [x] Use this MapRemoteEntry to implement the Map Remote List + Map Remote Edit screen -> Verify we can save, duplicate, create new, edit -> Work fine.
• [x] Ping @NghiaTranUIT to get HTTPHandler.swift and a demo, to understand how Map Remote works under hood.

For example:

• Map Remote changes the First Message Line and the Host Header of the capture request.

Additional Logic

• [x] As soon as we create or edit a new Map Remote Rule -> Notify the tunnel to close this alive connection with this host -> Verify it's closed.
• [x] Show the debugging tool in the Summary. Please note that the Notes row might change, depending on the Map Remote Entry config. See the flow.serveFromRemoteURL in MapRemoteService

[NghiaTranUIT]

4. Map Remote Logic

4.1 How to test manually (Localhost to Production)

1. Remove all Map Remote List and SLL proxying list
2. Use Postman and send http://localhost:3000/post?action=map_remote -> Verify the connection is failed because we don't have any localhost:3000 server
3. Right Click on the error request on Proxyman -> Tool -> Map Remote
4. Enter the following setting

5. Save
6. Make a request again or Repeat it
7. ✅ Verify the new URL becomes https://httpbin.proxyman.app

8. Open Map Remote -> Edit the first rule -> Tick Preserve the original URL
9. Save -> Repeat the request again
10. ✅ Verify the URL is preserved and have the new Summary Note

Video Demo

https://github.com/ProxymanApp/proxyman-windows-linux/assets/5878421/aa510e72-ea26-47ef-821a-b2d0b1b8130e

4.2 How to test manually (Production to Localhost)

1. Install docker and start a local httpbin: $ docker run -p 80:80 kennethreitz/httpbin

2. Verify we can call: http://127.0.0.1/get?id=123 in cURL or postman

3. Use Postman and send: https://httpbin.proxyman.app/get?id=123

4. Right Click on the request on Proxyman -> Tool -> Map Remote

5. Enter the following setting:

   

6. Repeat the request

7. ✅ Verify we get the response from the httpbin.org docker