[Feature] Support predicate receiving Request interface to match while routing in page.route(url, handler)

[Kremliovskyi]

Continuation of #6199
In my project we use GraphQL where all requests have the same URL but differs only in body. In order to use page.route(url, handler) I have to first retrieve body of request and make some checks if this is the request I am looking for. This function page.route(url, handler) does not support predicate with Request interface which makes impossible to stub requests when using GraphQL.

I envision it like this:

    async routeFindingRequests(stringToSearch) {
        
        // request instead of URL here
        await this.page.route(request => {
           return request.postData().includes(stringToSearch)
        }, route => {
            route.fulfill({
                body: JSON.stringify({
                    someKey: "someValue"
                })
            })
        })
    }

I would like to ask you to add the ability to work with request in addition to URL in page.route(url, handler) as this is blocker for using playwright.

P.S. Initially I thought there is a need to have async predicate but I see almost all functions are synchronous in Request interface. Thus I made a change above.

[mxschmitt]

note: I also had a use-case for that where I wanted to serve different responses based on the request http method.

[dgozman]

While there are no plans to add support for this, you can just route all the requests and call continue() vs fulfill():

await page.route('**/*', route => {
  if (route.request().postData().includes(stringToSearch))
    route.fulfill({ body: 'Some body' });
  else
    route.continue();
});

[Kremliovskyi]

Awesome, thank you.

[Kremliovskyi]

@dgozman It is working flawlessly. I suggest that you add your example to documents and close this ticket, no need to implement my suggestion.

[pavelfeldman]

Closing as per above, please feel free to open a new issue if this does not cover your use case.