add referer header to #api_verification_entreprise #471
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
grosser
approved these changes
Sep 14, 2025
Collaborator
grosser
left a comment
grosser
left a comment
There was a problem hiding this comment.
looks reasonable and safe 👍
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
PR to fix #470.
According to #470, when verifying the
reCAPTCHAtoken withverify_recaptcha, the HTTP request sent to Google's endpoint does not include a Referer header. Google rejects the request with a 403 Permission Denied error because the request lacks the expected referer/origin information.This PR adds a Referer header during
api_verification_enterprisemethod with a default value ofRails.application.default_url_options[:host].Any improvement is welcome !
Pre-Merge Checklist