-
-
Notifications
You must be signed in to change notification settings - Fork 664
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: nodejs/undici
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v7.9.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: nodejs/undici
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v7.10.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 11 commits
- 22 files changed
- 10 contributors
Commits on May 12, 2025
-
Add "clientTtl" option to close and remove connections from the pool …
…after a specified time. (#4175) Co-authored-by: Carlos Fuentes <me@metcoder.dev>
Configuration menu - View commit details
-
Copy full SHA for faca33a - Browse repository at this point
Copy the full SHA faca33aView commit details -
Signed-off-by: Matteo Collina <hello@matteocollina.com>
Configuration menu - View commit details
-
Copy full SHA for bf4c199 - Browse repository at this point
Copy the full SHA bf4c199View commit details
Commits on May 13, 2025
-
* add node v24 workflow * fix http2 test * update wpt status
Configuration menu - View commit details
-
Copy full SHA for 2ed2a8a - Browse repository at this point
Copy the full SHA 2ed2a8aView commit details
Commits on May 14, 2025
-
Co-authored-by: Uzlopak <5059100+Uzlopak@users.noreply.github.com>
1Configuration menu - View commit details
-
Copy full SHA for dcf82a7 - Browse repository at this point
Copy the full SHA dcf82a7View commit details
Commits on May 17, 2025
-
Configuration menu - View commit details
-
Copy full SHA for d6deb77 - Browse repository at this point
Copy the full SHA d6deb77View commit details
Commits on May 18, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 1262f61 - Browse repository at this point
Copy the full SHA 1262f61View commit details
Commits on May 20, 2025
-
fix: agent memory leak (#4223)
* fix: agent memory leak * fix: mock-agent
Configuration menu - View commit details
-
Copy full SHA for 59940c8 - Browse repository at this point
Copy the full SHA 59940c8View commit details -
Add ability to detect when MemoryCacheStore reaches max size (#4224)
* Initial impl * modified failing test * modified a comment * moved tests in memory-cache-store-size.js to memory-cache-store-tests.js
Configuration menu - View commit details
-
Copy full SHA for a8d280c - Browse repository at this point
Copy the full SHA a8d280cView commit details -
feat(ProxyAgent): match Curl behavior in HTTP->HTTP Proxy connections (…
…#4180) * feat(ProxyAgent): match Curl behaviour for http-http Proxy connections Curl does not send a CONNECT request for to a Proxy server, by default, for cleartext communications to an endpoint, via a cleartext connection to a Proxy. It permits forcing a CONNECT request to be sent via the --tunnelproxy parameter. This change modifies ProxyAgent's constructor to accept a `tunnelProxy` option, sends a CONNECT if either `tunnelProxy` is true, or either the Proxy or endpoint use a non-http: protocol. Disabling tunneling for HTTP->HTTP by default would be a breaking change, so currently, the tunneling behaviour requires an opt-out. This may change depending on feedback during code review. This adds a new test case which explicitly disables tunneling for an HTTP->HTTP connection, and asserts that no CONNECT message is sent to the server or proxy, and that the expected HTTP request is sent to the proxy. Closes #4083 * Part 2 This version tries to expose less sketchiness -- it's not particularly well organized yet, and I'm sure it could be cleaned up a lot. Instead of adding the "rawSocket" stuff to RequestOptions, there's a new wrapper ProxyClient added, which intercepts the CONNECT message and prevents it from being dispatched. Unfortunately the wrapper client isn't quite written in a way to manage all of the client-ness, so ProxyAgent is still responsible for updating the PATH of HTTP->HTTP Proxy requests to include the endpoint domain. It is messy though, admittedly. * remove rawSocket from Dispatcher type definition * Add some docs * rename to proxyTunnel to match CURL * Rename to in the docs, too * Try to clarify the docs a bit initially just wanted to fix a typo, but thought maybe the original explanation wasn't great.
Configuration menu - View commit details
-
Copy full SHA for 95fd9d3 - Browse repository at this point
Copy the full SHA 95fd9d3View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9e0cfcb - Browse repository at this point
Copy the full SHA 9e0cfcbView commit details -
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 5ad8998 - Browse repository at this point
Copy the full SHA 5ad8998View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v7.9.0...v7.10.0