fetch
http-proxy
fetch | http-proxy | |
---|---|---|
35 | 14 | |
2,078 | 13,743 | |
0.5% | 0.2% | |
5.9 | 0.0 | |
6 days ago | 5 days ago | |
HTML | JavaScript | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
fetch
- JavaScript fetch does not support GET request with body
-
GitHub Engineering: When MTLS Is Done Wrong
mTLS has warts when used cross-origin. Fetch spec says that pre-flight requests mustn't include client certificates[1], so as a consequence servers behind mTLS authenticated proxy won't get a chance to reply to those pre-flight. Yet for non-preflighted requests it's fine to include client certificates..
[1] https://fetch.spec.whatwg.org/#cors-protocol-and-credentials
-
Node.js fetch() vs. Deno fetch(): Implementation details...
I've been testing full duplex streaming from and to the browser using fetch() in a Native Messaging host. (No browser currently support full duplex streaming even though HTTP/2 does, see Fetch body streams are not full duplex #1254).
-
How do I detect requests initiated by the new fetch standard? How should I detect an AJAX request in general?
Most js libraries use XMLHttpRequest and so provide HTTP_X_REQUESTED_WITH: XMLHttpRequest, but neither Chrome's implementation nor Github's polyfill of the new fetch uses a similar header. So how can one detect that the request is AJAX?
-
Server Sent Events
Any resource of significance should be given a URI. https://www.w3.org/DesignIssues/Axioms.html#uri
Or alternatively,
> Cool URLs don't change (implicitly, cool things have URLs, see above). https://www.w3.org/Provider/Style/URI
The advantage would be so high. It'd become a standard way to assert a resource, to make known a fact, that would be viable across systems. Instead of pushing to a chat app an anonymous chat message in a room, the server could assert a /room/42/msg/c0f3 resource, could identify universally what it is it's sending.
We have come glancingly close to getting such a thing so many times. The HyBi mailing list that begat websockets had a number of alternate more resourceful ideas floating around such as a BEEP protocol that allowed patterns beyond request/response of resources. The browser actually implements an internal protocol that uses HTTP2/push to send resourceful messages... Even though http2/push was de-implemented for webserving in general, and even though ability to hear push events was never implemented (oft requested).
The best we have today is to stream json-ls events, which have an @id property identifying them. But developers would have to snoop these events, and store them in a service worker, to make them actually accessible as http resources.
I continue to hold hope eventually we'll get better at using urls to send data, to assert new things happening... But it's been nearly 30 years of me hoping, and with some fleeting exceptions the browser teams have seemed disinterested in making urls cool, in spite of a number of requests. https://github.com/whatwg/fetch/issues/65 was an old request. https://github.com/whatwg/fetch/issues/607 had some steam in making it happen.
-
[Express] - How to have a self-updating display in browser window? Template Engines sufficient? Or use Vue/Angular/React?]
Fetch
-
Adding timeout and multiple abort signals to fetch() (TypeScript/React)
Proposal: fetch with multiple AbortSignals - I got the idea of merging multiple signals from here.
-
My experience being blocked by Google Safe Browsing
Port 10080 is blocked on most browsers[0] per the WhatWG "bad ports" list[1]. That particular port was added to the list due to the Slipstream attack[2] that made the news a few years ago[3].
You don't have to switch to a browser that ignores standard security mitigations. Just pick a different port for your service.
[0] I just tested Chrome, Firefox, and Safari.
[1] https://fetch.spec.whatwg.org/#bad-port
[2] https://samy.pl/slipstream/
[3] https://news.ycombinator.com/item?id=24955891
-
Substack is now powered by Ghost
Note that caching resources across sites isn't really a thing anymore. See https://github.com/whatwg/fetch/issues/904
- Help with HTTP requests
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"
What are some alternatives?
cors-anywhere - CORS Anywhere is a NodeJS reverse proxy which adds CORS headers to the proxied request.
axios - Promise based HTTP client for the browser and node.js
undici - An HTTP/1.1 client, written from scratch for Node.js
node-fetch - A light-weight module that brings the Fetch API to Node.js
deno - A modern runtime for JavaScript and TypeScript.
ky-universal - Use Ky in both Node.js and browsers
cors-playground
gh-got - Convenience wrapper for Got to interact with the GitHub API
university-domains-list - University Domains and Names Data List & API
Nock - HTTP server mocking and expectations library for Node.js
set-cookie-parser - Parse HTTP set-cookie headers in JavaScript
got - 🌐 Human-friendly and powerful HTTP request library for Node.js