fix: use full browser User-Agent for investing.com requests #8
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.


investing.com rejects requests with truncated User-Agent "Mozilla/5.0", returning 403 Forbidden. Using a complete Chrome UA string fixes this.
Generated with Claude Code via Happy
Note
Low Risk
Low risk: only adjusts outbound request headers to a third-party service; main risk is potential fragility if Investing.com changes UA requirements.
Overview
Updates the Investing.com earnings/IPO calendar HTTP request headers to send a full Chrome browser
User-Agentstring (instead of a truncatedMozilla/5.0) to avoid403 Forbiddenresponses when fetching calendar data.Written by Cursor Bugbot for commit 7c578dd. This will update automatically on new commits. Configure here.