Requestly VS http-proxy

Requestly- Makes frontend development cycle 10x faster with API Client, Mock Server, Intercept & Modify HTTP Requests and Session Replays.

[1]: https://github.com/requestly/requestly/

If you want to intercept and modify a incoming json response for some specific url pattern, would a service worker be a good way to do so?

To illustrate, assume I frequently browse example.com and want to trick my browser into thinking that I have "favorited" every post. It's trivial to write a for loop that iterates over response.json and sets `is_favorite = true`. But it's not as clear to me where this script should ideally live in order to have the logic always executed before the response is made available to the site.

Your comment made me think about whether I can replace my overkill solution (https://requestly.io/) with something lightweight.

If you prefer open-source there is Requestly and Toolkit.

If you don't know Requestly, It is an open-source Chrome/Firefox/Edge extension to intercept & modify HTTP requests & responses. One of the popular features is to modify HTTP headers. We also offer workspaces for easy collaboration between team members.

Hey, open-source community, This is Sachin, One of the core maintainers of Requestly - An open-source alternative to Charles Proxy & Telerik Fiddler. In case you don’t know about Charles Proxy & Fiddler, both of them are two decades-old products used widely to Inspect & Modify HTTP traffic in web & mobile apps.

In /etc/hosts file you put only IP addresses and hostnames, i.e. 127.0.0.1 cdn.cloudflare.steamstatic.com. Then you have to set up a web server on localhost port 80 and put your image at http://localhost/steamcommunity/public/images/apps/753/1d0167575d746dadea7706685c0f3c01c8aeb6d8.jpg as well as other files from https://cdn.cloudflare.steamstatic.com. You also have to keep the URLs updated when they change upstream. It's not worth it. Better use a local proxy server like mitmproxy or requestly.

Requestly founder here. You are essentially looking for Requestly - A Chrome/Firefox browser extension to Intercept & Modify HTTP requests. Using Requestly you can actually do the following things

For development/Debugging: 1. VSCode - Got used to the key bindings and integrated terminal, so now it's really hard to switch 2. Requestly - For easily setting up local debugging environments. I am less of a UI guy, so this allows me to use the live UI of a deployed site, and redirect whichever request I want to play with to my local server. 3. Wireshark - To better understand a network protocol.

[0]: https://requestly.io

Take a look at https://github.com/http-party/node-http-proxy , specifically their .web() helper

I have been tasked with writing a proxy server that takes a clients requests and forwards it to a target server (normal proxy stuff). The client and the target are out of my control. The only change in the client is that the its requests to the proxy server instead of the target. Now, what I need to do is modify the response from target because the client expects it in a certain format and the server responds with a different format. I have a working implementation using http-proxy (https://github.com/http-party/node-http-proxy) that works over HTTP . But I need it to work over HTTPS, I can't make much sense of the documentation and I can't find any additional resources on how HTTPS can be implemented. The client-proxy and proxy-target connection both need to be encrypted(HTTPS). I found solutions using different tools but they mostly seem to be encrypted end to end, so the proxy can't read the response data(I need to be able to modify it). Any ideas on how I can do this?

What you're describing is a proxy server. If you wanted to use Node.js check out https://github.com/http-party/node-http-proxy. Notice that the examples there just forward the req though which potentially has identifying information like cookies, so you'll need to rework to anonymize. Should be straightforward.

There's several ways to have a blog path contain a separate setup from the marketing/product routes.

One is to run a reverse proxy on the root domain to pull in separate routes for various services.

https://github.com/http-party/node-http-proxy

You can do rewrites at the server level for the root domain

Or if the app on the root domain can do the routing for you (have done this before with a Rails app)

Check the documentation of the http-proxy-middleware library (and of the node-http-proxy library, used under-the-hood) to learn how you can manipulate the proxied request & response.

Relevant node-http-proxy issue: https://github.com/http-party/node-http-proxy/issues/230

I'm running Node app in Heroku which is using node-http-proxy, and I've given my Heroku app the domain "example.com"