fix: normalize content-type header check for case insensitivity #255
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.
Summary
This PR addresses an issue where the
content-typeheader check was case-sensitive, causing validContent-Typevalues likeText/htmlto be rejected. The solution normalizes thecontent-typeheader using.toLowerCase()to ensure case-insensitive checks.Reproduction Steps
Page must return a header content-type with text/Content-Typeheaders.Changes Made
content-typecheck in the scraper logic to usetoLowerCase().Content-Type: Text/htmlnow works as expected.