fix(crawler): usa fetch compatibile con undici - #99
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cosa cambia
fetcheAgentdalla stessa installazione diundiciPerché
Il client mescolava il
fetchintegrato di Node con unAgentdiundici8. Le due implementazioni non condividono il protocollo interno del dispatcher e ogni scan falliva conUND_ERR_INVALID_ARG: invalid onRequestStart method.Impatto
Ripristina gli scan reali preservando DNS pinning, controllo SSRF, budget, redirect, limiti e riuso delle connessioni.
Verifiche
npm run checknpm run test:coveragenpm run sentinel -- scan --dry-runsui tre monitor configurati