allow passthrough for undefined routes / graphql interferes with passthrough
See original GitHub issueDescribe the solution you’d like
I’d like to be able to allow certain matching urls to be passed through and handled normally instead of intercepting and giving 404.
Describe alternatives you’ve considered
Seems like a lot of work to manually define ctx.fetch
for each request I would want to pass through on some wildcard domain / string match.
Issue Analytics
- State:
- Created 3 years ago
- Comments:16 (9 by maintainers)
Top Results From Across the Web
Authentication and authorization - Apollo GraphQL Docs
Authentication is determining whether a given user is logged in, and subsequently determining which user someone is.
Read more >Request matching - Basics - Mock Service Worker Docs
Requests with no corresponding request handlers are performed as-is (bypassed). Request matching substantially differs based on the request ...
Read more >GraphQL Is a Trap?
GraphQL is great solution to organizational problem of slow communication and/or misaligned incentives between frontend and backend teams. GraphQL is ...
Read more >Responses | Strapi Documentation
PassThrough ; app.use(async ctx => { ctx.body = someHTTPStream.on('error', ... If string is used message parameter must be null. null and undefined will...
Read more >express-graphql : context is always undefined
Apparently you need to pass through context manually like so: app.use('/graphql', [auth_middleware, bodyParser.json()], (req, res) => graphqlExpress({ ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
thanks @kettanaito , just upgraded to
0.20.5
and it works without the empty handlers!@kettanaito I could use this feature as well for testcafe support. testcafe has some internal posts it makes back to it’s proxy server, and we can’t add headers to those requests. I noticed that if i just add
resolve(getOriginalResponse());
to theINTERNAL_ERROR
handler in mockServiceWorker.js it works, but that felt wrong to do.