HTTP hijacking (for Node WS/CONNECT, etc...)

[piscisaureus]

No description provided.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

[jimmywarting]

how about something service-worker ish implementation?

/** @param {FetchEvent} evt */
function handleFetch (evt) {
  const { request, respondWith } = evt
  respondWith( new Response(...) )
}

globalThis.onfetch = handleFetch

[bartlomieju]

how about something web-worker ish implementation?

/** @param {FetchEvent} evt */
function handleFetch (evt) {
  const { request, respondWith } = evt
  respondWith( new Response(...) )
}

globalThis.onfetch = handleFetch

@jimmywarting is onfetch specced anywhere or is just an idea?

[jimmywarting]

https://developer.mozilla.org/en-US/docs/Web/API/ServiceWorkerGlobalScope/onfetch

[crowlKats]

I dont see how that is relevant to this issue. that is just the fetch event that we have on deploy, it has nothing to do with this

[jimmywarting]

then i must have misinterpreted what the issue is about, i tough it was to hijack/intercept a ongoing request

eg: making a fetch call to get something would trigger a fetch event that you could use to monitor/log all outgoing request. (unless that's what PerformanceEventTiming will be for, but a fetch event could for higher level stuff

globalThis.onfetch = evt => {
  // hijiack the request and respond with mocked data instead
}

fetch('https://httpbin.org/get') // would trigger a fetch event

[crowlKats]

Ah, no this is something completely different, though the issue name is not great and there isnt a description, so cant blame you.
Basically this is about an API to get the underlying tcp/tls stream of a request, so one can implement custom protocols that are based on http (ie websocket)