http-proxy
http-proxy-middleware
Our great sponsors
http-proxy | http-proxy-middleware | |
---|---|---|
14 | 5 | |
13,736 | 10,483 | |
0.4% | - | |
0.0 | 5.5 | |
4 days ago | 4 days ago | |
JavaScript | TypeScript | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
http-proxy
-
Is there a way to accept incoming http but outgoing must be https?
Take a look at https://github.com/http-party/node-http-proxy , specifically their .web() helper
-
HTTPS proxy setup with response modification
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's the stack for this application?
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.
- What libraries should I use to map multiple ports into a single one with node.js?
-
GraphQL is now available on Supabase
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)
- Launch HN: Requestly (YC W22) – Network debugging proxy for web and mobile
-
Creating and deploying a tiny proxy server on Vercel in 10 minutes
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.
-
How to create a simple forward proxy
Relevant node-http-proxy issue: https://github.com/http-party/node-http-proxy/issues/230
- The history and reasons behind CORS, and how to use it
-
Heroku equivalent/alternative to editing local hosts file?
I'm running Node app in Heroku which is using node-http-proxy, and I've given my Heroku app the domain "example.com"
http-proxy-middleware
-
About Reverse Proxy
Then we translate each rule. webpack-dev-server uses http-proxy-middleware under the hood, and here's how to translate each field.
-
Error proxying Node gateway to Flask server. I have not encountered when trying to proxy to Node server. Any help would be greatly appreciated. Here is the code for the api gateway, the flask server and the error message itself:
Oh and you might wanna take a look at the github for the proxy middleware library under the ECONNREFUSED section
-
What libraries should I use to map multiple ports into a single one with node.js?
Actually I'm receiving errors like The resource from “http://localhost:8090/Sidebar/Sidebar.css” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff)... Both my css and js files are gettings "text/html" on their headers and changing the http-proxy-middleware options doesn't seem to change it... On their GitHub there's an issue about it: https://github.com/chimurai/http-proxy-middleware/issues/580 ... And they say that it's a webpack issue: https://github.com/froala/angular-froala/issues/170 ... But these solutions on the second page don't work for me.
-
Creating and deploying a tiny proxy server on Vercel in 10 minutes
// Create a proxy to redirect requests of the "/api/*" path to "https://example.org". // // Examples: // GET /api/hello → GET https://example.org/hello // POST /api/test?color=red → POST https://example.org/test?color=red // // Additionally, the proxy will: // - Add an "x-added" header // - Remove the "x-removed" header // From the proxied response. // // You can/should update the proxy to suit your needs. // See https://github.com/chimurai/http-proxy-middleware for more details. const { createProxyMiddleware } = require('http-proxy-middleware'); const apiProxy = createProxyMiddleware({ target: "https://example.org", changeOrigin: true, pathRewrite: { "^/api": "" // strip "/api" from the URL }, onProxyRes(proxyRes) { proxyRes.headers['x-added'] = 'foobar'; // add new header to response delete proxyRes.headers['x-removed']; // remove header from response } }); // Expose the proxy on the "/api/*" endpoint. export default function (req, res) { return apiProxy(req, res); };
What are some alternatives?
axios - Promise based HTTP client for the browser and node.js
parsec 🌌 - 🌌 Tiniest body parser in the universe. Built for modern Node.js
node-fetch - A light-weight module that brings the Fetch API to Node.js
fastify-webpack-hot - A Fastify plugin for serving files emitted by Webpack with Hot Module Replacement (HMR).
ky-universal - Use Ky in both Node.js and browsers
tinyws - 🚡 tiny WebSocket middleware for Node.js
gh-got - Convenience wrapper for Got to interact with the GitHub API
mean - The MEAN stack uses Mongo, Express, Angular(6) and Node for simple and scalable fullstack js applications
Nock - HTTP server mocking and expectations library for Node.js
node - Node.js JavaScript runtime ✨🐢🚀✨
got - 🌐 Human-friendly and powerful HTTP request library for Node.js
vercel - Develop. Preview. Ship.