New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose standard fetch/Request API for request interception #26
Comments
There's a project which might help: https://github.com/bitinn/node-fetch |
aslushnikov
added a commit
that referenced
this issue
Jun 28, 2017
This patch does a step towards Fetch API: - implements Request object to some extend. The Request object will be sent in RequestWillBeSent event. - implements InterceptedRequest which extends from Request and allows for request modification. The InterceptedRequest does not conform to Fetch API spec - there seems to be nothing related to amending in-flight request. - adds test to make sure that request can change headers. References #26
aslushnikov
added a commit
that referenced
this issue
Jun 28, 2017
This patch introduces the 'request' event which is fired when page has initiated a request. The event dispatches an instance of Request class. References #26.
aslushnikov
added a commit
that referenced
this issue
Jun 29, 2017
This patch implements NetworkManager, which encapsulates all the interaction with Network domain. The NetworkManager also uses partial implementation of Request and Response classes, defined in the Fetch API specification. References #26
aslushnikov
added a commit
that referenced
this issue
Jun 30, 2017
This patch adds support to redirects so that they will be reported as a separate requests. References #26.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should use standard request definition from https://developer.mozilla.org/en-US/docs/Web/API/Request, user should be able to intercept and fetch requests similarly to web service workers.
The text was updated successfully, but these errors were encountered: