Robert Nagy
Robert Nagy
> I think we should keep it maximally flexible and pass in the request options. That won't work though? You can have different request options that have the same result....
> as different hosts could provide unrelated responses with the same path. Am I missing something? If different host can provide unrelated responses then they should reply with `Vary: host`....
> Cache is always split per URL, and Vary only adds additional granularity within the single URL. > > (Cache is technically also split per method, but PUT/POST invalidates cached...
Can you try to use the undici package instead of the bundled version? To see if the problem still occurs in newer versions of undici.
@jandppw Have you considered simply using `undici.request` which is our recommended API? fetch should only be used if you require compatibility with other runtimes than NodeJS.
> Is there any documentation on that? Not sure. Where would you expect that to be documented? > We were under the impression that fetch is the generic way to...
With streams you can have multiple consumers consuming the response with different speeds. We should only do this for requests where the response body can be fully buffered into memory.
I believe I open end an issue over at elasticsearch a long time ago. They don't properly cleanup signals.
https://github.com/elastic/elasticsearch-js/issues/1716
@mcollina @ShogunPanda @metcoder95 - Should we have separate controllers for request and response or just one for both or just the response? In theory the request and response can propagate...