Conversation
|
I've been wondering about the implementation here and I think we should instead of asking users to prepare files by adding a suffix for resolver information for each entry, rather have a command line option for this. I'm thinking something along the lines of This obviously removes the ability to have per input file entry overrides like this PR gives, (I'm not sure about a use case where the same domain will need to have different resolution's), but makes parsing simpler while also making it compatible with any reader. Anyone have thoughts? |
I like the TL;DR your command line approach and format is best given the constraints. |
Turns out I was wrong. The |
|
I raised a simple PR that passes through the host resolver rules as an option here: #309 |
Hi, it seems I'm not alone who wants this feature:
Basically it checks whether input urls for
scan filemode ends with##<ipaddr>and utilizeshost-resolver-rulesandhost-ruleschrome flags (chromedp/chromedp#985 (comment))##<ipaddr>is cutted from the end before passed into chromedp.Navigateexample usage:
example output:
