Patch: save correct headers for XHR requests #631
Merged
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.
None of the headers of XHR requests are outputted when performing headless crawls with the
-xhr
flag set:The headers will always be
null
becausehttpreq.Header
is used (see here), which uses the crawler's headers. Instead, the headers from the fetch request should be used.Here is the output from running the same command above, but with the changes incorporated in this pull request: