starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #325] Enable running proxy as a backend for Request Capture #119

New issue

Closed

opened 2026-03-16 13:31:15 +03:00 by kerem · 12 comments

kerem commented

2026-03-16 13:31:15 +03:00

Owner

Originally created by @guilt on GitHub (Nov 22, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/325

Often, while writing new clients, or debugging existing API's, it is often useful to use a tool such as Charles Proxy. It allows one to save traces (request + response) and reload them again for reviewing as well.

Would be useful if Postwoman came up with a way to act as such a proxy, and one could connect existing apps / browsers on them, and look through the requests / responses. Would also be helpful to generate user signed certificates if one wishes to debug through TLS encrypted requests as well.

Ask:

A standard way to load and import traces, to begin with. Please support existing HTTP capture trace formats, such as Charles' .trace files etc.
Look at actually enable the proxying feature.
Enable support for saving traces as well, so they can be reused later across app sessions.

Alternatives:
N/A

Additional Context:
N/A

Originally created by @guilt on GitHub (Nov 22, 2019). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/325 **Often, while writing new clients, or debugging existing API's, it is often useful to use a tool such as Charles Proxy. It allows one to save traces (request + response) and reload them again for reviewing as well.** Would be useful if Postwoman came up with a way to act as such a proxy, and one could connect existing apps / browsers on them, and look through the requests / responses. Would also be helpful to generate user signed certificates if one wishes to debug through TLS encrypted requests as well. Ask: 1. A standard way to load and import traces, to begin with. Please support existing HTTP capture trace formats, such as Charles' .trace files etc. 2. Look at actually enable the proxying feature. 3. Enable support for saving traces as well, so they can be reused later across app sessions. Alternatives: N/A Additional Context: N/A

kerem

2026-03-16 13:31:15 +03:00

closed this issue
added the
discussion

need information
labels

kerem commented

2026-03-16 13:31:31 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 22, 2019):

Hi there!
Postwoman have proxy support! It allows you to request responses from restricted endpoints, hide your IP, avoid CORS issues and other functionalities.

Proxy mode is global so it'll be also enabled for GraphQL testing too.

To turn on Proxy; Settings > Proxy

@liyasthomas commented on GitHub (Nov 22, 2019): Hi there! Postwoman have proxy support! It allows you to request responses from restricted endpoints, hide your IP, avoid CORS issues and other functionalities. Proxy mode is global so it'll be also enabled for GraphQL testing too. To turn on Proxy; Settings > Proxy

kerem commented

2026-03-16 13:31:36 +03:00

Author

Owner

@guilt commented on GitHub (Nov 23, 2019):

Okay, maybe I wasn't talking about using a proxy, but being one, so that other apps could connect to Postwoman, and we can see the requests on it, and capture them for future use

@guilt commented on GitHub (Nov 23, 2019): Okay, maybe I wasn't talking about using a proxy, but being one, so that other apps could connect to Postwoman, and we can see the requests on it, and capture them for future use

kerem commented

2026-03-16 13:31:41 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 23, 2019):

Oh! my mistake while interpreting that. Let's discuss over it.
Do you have any use cases or existing projects that does this?

@liyasthomas commented on GitHub (Nov 23, 2019): Oh! my mistake while interpreting that. Let's discuss over it. Do you have any use cases or existing projects that does this?

kerem commented

2026-03-16 13:31:46 +03:00

Author

Owner

@guilt commented on GitHub (Nov 23, 2019):

Yes. I routinely use app packet captures to identify request patterns, time between requests and would like to save some of them for later.

It's way easier than me trying to type out all the parameters, is to fill it from an existing source.

@guilt commented on GitHub (Nov 23, 2019): Yes. I routinely use app packet captures to identify request patterns, time between requests and would like to save some of them for later. It's way easier than me trying to type out all the parameters, is to fill it from an existing source.

kerem commented

2026-03-16 13:31:52 +03:00

Author

Owner

@guilt commented on GitHub (Nov 26, 2019):

I was looking around for libraries so I could explain this, a starting point may be to look at: https://github.com/alibaba/anyproxy and see if possible to integrate their code / libraries(?)

More importantly, the point of proxying may not be to allow TCP connect / tunnel, but more about per-request capturing and debugging. So HTTP CONNECT method isn't what the solution will do.

@guilt commented on GitHub (Nov 26, 2019): I was looking around for libraries so I could explain this, a starting point may be to look at: https://github.com/alibaba/anyproxy and see if possible to integrate their code / libraries(?) More importantly, the point of proxying may not be to allow TCP connect / tunnel, but more about per-request capturing and debugging. So HTTP CONNECT method isn't what the solution will do.

kerem commented

2026-03-16 13:31:57 +03:00

Author

Owner

@NBTX commented on GitHub (Nov 28, 2019):

What if we added the functionality to the proxy server to act as a packet capture and then pass this to the postwoman interface?

So a workflow would be:

setup a copy of the Postwoman proxy server and enable some packet capture option.
connect the Postwoman app to the proxy server as usual.
connect to the proxy server on the intended device and perform the requests that you wish to be logged.
packets are logged in a packet capture tab in Postwoman.

@NBTX commented on GitHub (Nov 28, 2019): What if we added the functionality to the proxy server to act as a packet capture and then pass this to the postwoman interface? So a workflow would be: 1. setup a copy of the [Postwoman proxy server](https://github.com/NBTX/postwoman-proxy/) and enable some packet capture option. 2. connect the Postwoman app to the proxy server as usual. 3. connect to the proxy server on the intended device and perform the requests that you wish to be logged. 4. packets are logged in a packet capture tab in Postwoman.

kerem commented

2026-03-16 13:32:02 +03:00

Author

Owner

@guilt commented on GitHub (Dec 5, 2019):

That's a very useful start :) Would love to see this in action.

@guilt commented on GitHub (Dec 5, 2019): That's a very useful start :) Would love to see this in action.

kerem commented

2026-03-16 13:32:07 +03:00

Author

Owner

@liyasthomas commented on GitHub (Dec 25, 2019):

@NBTX think this issue fits better in proxy repo.

@liyasthomas commented on GitHub (Dec 25, 2019): @NBTX think this issue fits better in proxy repo.

kerem commented

2026-03-16 13:32:12 +03:00

Author

Owner

@NBTX commented on GitHub (Dec 26, 2019):

For sure. (You'll need to transfer the issue.)

@NBTX commented on GitHub (Dec 26, 2019): For sure. (You'll need to transfer the issue.)

kerem commented

2026-03-16 13:32:17 +03:00

Author

Owner

@liyasthomas commented on GitHub (Dec 27, 2019):

Issues can only be transferred in between repos under same profile. Can't transfer to an organization.

@liyasthomas commented on GitHub (Dec 27, 2019): Issues can only be transferred in between repos under same profile. Can't transfer to an organization.

kerem commented

2026-03-16 13:32:22 +03:00

Author

Owner

@Congee commented on GitHub (Jan 14, 2020):

This feature is helpful when you reverse-engineer an api. I currently use Fiddler, mitm-proxy, or Charles.

@Congee commented on GitHub (Jan 14, 2020): This feature is helpful when you reverse-engineer an api. I currently use Fiddler, mitm-proxy, or Charles.

kerem commented

2026-03-16 13:32:27 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jan 15, 2020):

Transferred this issue to https://github.com/postwoman-io/postwoman-proxy/issues/10

@liyasthomas commented on GitHub (Jan 15, 2020): Transferred this issue to https://github.com/postwoman-io/postwoman-proxy/issues/10

kerem referenced this issue

2026-03-17 00:07:46 +03:00

[PR #119] [MERGED] Bump vuex-persist from 2.0.1 to 2.1.0 #2422