feat(tool-page): support visit pages with header#712
feat(tool-page): support visit pages with header#712clChenLiang wants to merge 2 commits intoChromeDevTools:mainfrom
Conversation
| headers: zod | ||
| .record(zod.string()) | ||
| .optional() | ||
| .describe('Optional headers to send with the navigation request.'), |
There was a problem hiding this comment.
the headers would be sent for all requests on the page until the headers are removed so this description is not correct. Could you clarify what use case you have? Would #692 work better for the use case? cc @natorion @Lightning00Blade
There was a problem hiding this comment.
we always have an application, which will be test in a prod env.
this test condition, need to divide different with really prod env which user use.
the best way, is to use a special headers
There was a problem hiding this comment.
the #692 send with header in the whole mcp lives.
may be in this, can be more flexible
|
Closing as stale. The current implementation in this PR leaks headers beyond individual navigations. The ideal solution would be to either have a separate parameter in emulate tool or remove extra headers after the navigation is done. |
2 participants
support to visit some page with special headers