Hacker GitHub

← All repos

whatwg/fetch

View on GitHub ↗ ★ 2,258 HTML

Fetch Standard

33 mentions on Hacker News by 22 people: 1 story, 32 comments · first 2016-04-02 · latest 2026-06-23

Mentions per year 33 mentions · busiest year 2022 (13)
20082026
  1. …are usually meant more for one-shot access. QUERY is meant to address these limitations. [1]: https://github.com/whatwg/fetch/issues/551
    comment by EnnEmmEss · 2026-06-23 · in The new HTTP QUERY method explained
  2. …the relavent spec said it should work, until it was deprecated and removed from the standard https://github.com/whatwg/fetch/pull/1166 With flash - that might all be true, but there was a time when many websites required it. It might not…
    comment by bawolff · 2025-11-01 · in Intent to Deprecate and Remove XSLT
  3. …last few years. There has been a lot of pushback against supporting full-duplex streams[0]. [0]: https://github.com/whatwg/fetch/issues/1254
  4. …(just documenting, the discussions have already happened). You can follow along here if you'd like: https://github.com/whatwg/fetch/issues/1739
    comment by patrickmeenan · 2024-09-15 · in Compression Dictionary Transport
  5. …a good chance to make use of Push! We can't see Pushes coming at us, cant be responsive to them! https://github.com/whatwg/fetch/issues/51 It also feels like the use case everyone was focusing on/acknowlegding of content delivery had…
    comment by jauntywundrkind · 2024-09-06 · in Intent to unship: HTTP/2 Push
  6. ▲ 6
    WHATWG's stance: No support for GET requests with body in Fetch API
    story by gearnode · 2023-11-21 · 0 comments
  7. Full duplex streaming (which Deno supports) would be even nicer. Not yet part of the WHATWG Streams: https://github.com/whatwg/fetch/issues/1254
    comment by ignoramous · 2023-07-22 · in Bun v0.7.0
  8. …when it was available, it lacked the oft requested ability to get notice of new pushed resources. ( https://github.com/whatwg/fetch/issues/65 was an old request. https://github.com/whatwg/fetch/issues/607 had some steam in making it…
    comment by rektide · 2023-05-15 · in Server-sent events
  9. …been, trying ro actually enjoy the new http standards; resistance on all fronts to real usage. [1] https://github.com/whatwg/fetch/issues/51
  10. Note that caching resources across sites isn't really a thing anymore. See https://github.com/whatwg/fetch/issues/904
    comment by bakkoting · 2022-12-12 · in Substack is (not) now powered by Ghost
  11. Maybe referring to GET, not POST/PUT bodies? https://github.com/whatwg/fetch/issues/83 Seems pretty short-sighted of a decision there, since XMLHTTPReq does it just fine, and it is in the HTTP RFC's
    comment by hobobaggins · 2022-08-20 · in Removing HTTP/2 Server Push from Chrome
  12. …bidirectionalism beyond request-response. [1] https://news.ycombinator.com/item?id=32514159 [2] https://github.com/whatwg/fetch/issues/607
    comment by rektide · 2022-08-19 · in Removing HTTP/2 Server Push from Chrome
  13. …Push support to fetch so developers could try out other uses for push. Seemingly ignored by chrome. https://github.com/whatwg/fetch/issues/607 Having the browser be a minimalist, picky implementation of http protocols is hard for me to…
    comment by rektide · 2022-08-18 · in Removing HTTP/2 Server Push from Chrome
  14. …issue tracker. Apparently, there is a new issue for it, so that might yet happen: [2]. [1]: https://github.com/whatwg/fetch/issues/34 [2]: https://github.com/whatwg/fetch/issues/981
    comment by twiss · 2022-08-08 · in Why does gRPC insist on trailers?
  15. …to implement them, but also without, ideally, giving Google the power to veto them). [1]: https://github.com/whatwg/fetch/issues/772
    comment by twiss · 2022-08-08 · in Why does gRPC insist on trailers?
  16. …. There's also a series of whatwg issues about exposing trailers in the fetch API: https://github.com/whatwg/fetch/issues/34 . For a protocol that sits above L7, the gRPC HTTP/2 protocol is liberal about diving past the semantics outlined…
  17. …never letting us try. Here's a good recent (4 year old) issue; it links back to much older issues. https://github.com/whatwg/fetch/issues/607 The rest of the protobuf world has gotten so much better. But the grpc on the web hacks feel bad.…
  18. …http is for. If it can't help them load pages off one of their CDNs faster, they don't care. [1] https://github.com/whatwg/fetch/issues/65
  19. …most basic follow-through on what they start. [1] https://datatracker.ietf.org/doc/html/rfc8030 [2] https://github.com/whatwg/fetch/issues/51 [3] https://groups.google.com/a/chromium.org/g/blink-dev/c/K3rYL...
    comment by rektide · 2022-02-20 · in Server-sent events, WebSockets, and HTTP
  20. There's a relevant spec issue here https://github.com/whatwg/fetch/issues/973
    comment by styfle · 2022-02-01 · in Fetch API has landed into Node.js
  21. There's a relevant spec issue you can follow here https://github.com/whatwg/fetch/issues/973
    comment by styfle · 2022-02-01 · in Fetch API has landed into Node.js
  22. This is fetch: https://github.com/whatwg/fetch https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API Here is discussion about it in Node with some (pretty old) discussion https://docs.google.com/document/d/1tn_-0S_FG_sla81wFohi8Sc8...
    comment by inglor · 2022-02-01 · in Fetch API has landed into Node.js
  23. A bit late for the original discussion, but in case it helps future readers, I've filed https://github.com/whatwg/fetch/issues/1295 to see if we can get the spec and browsers aligned. (My guess is we will update the spec to allow this and…
    comment by domenicd · 2021-08-14 · in Hosting SQLite Databases on GitHub Pages
  24. …to look this stuff up. I have a few commits to the spec, but I barely show up in the `git blame`. https://github.com/whatwg/fetch/graphs/contributors I've written articles about fetch in the past, but if I search Google for "fetch API" my…
  25. …WebTransport, &c. HTTP (almost) was here. [1] https://news.ycombinator.com/item?id=25064855 [2] https://github.com/whatwg/fetch/issues/51 Edit: there was a deleted comment saying that this kind of use case is not what Push was for, is not…
    comment by rektide · 2021-01-27 · in Data fetching on the web still sucks
  26. …can help it along, and that the world has a chance to use this amazing enhancement to HTTP. [1] https://github.com/whatwg/fetch/issues/65
    comment by rektide · 2020-12-03 · in HTTP/2 Push is dead
  27. …were so terrible at this. [1] https://developers.google.com/web/fundamentals/push-notifica... [2] https://github.com/whatwg/fetch/issues/65
  28. …fetch(), which uses promises as return type, do not support aborting requests, as discussed [here]( https://github.com/whatwg/fetch/issues/447 ) but the [old XMLHttpRequest does]( https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequ…
    comment by Guillaume86 · 2017-11-10 · in Simple React Patterns
  29. …multiple models, for the programmer to choose according to their particular use case. [1] https://github.com/whatwg/fetch/issues/27
    comment by lobster_johnson · 2017-01-05 · in Goroutines, Nonblocking I/O, and Memory Usage
  30. …& Web Push — something I expected to be at the bottom of the priority list for Apple's browser. [1] https://github.com/whatwg/fetch/issues/27
  31. This thread has a much more in-depth discussion on the considerations for designing this API: https://github.com/whatwg/fetch/issues/27 One key point is: since a promise can have multiple then-subscribers interested in it, (a) is it the…
  32. In fetch's defence it will in future once the Streams API is finalised: https://github.com/whatwg/fetch/issues/21
  33. …don't reject on non-2XX! I use axios instead. This is especially so sad when using async/await :( https://github.com/whatwg/fetch/issues/18 fetch(url) .then((res) => { if (res.statusCode < 200 || res.statusCode > 299) { throw new…