[PLUGINS-257: Sec-fetch header is checked to determine whether the re… #284
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.
1. Objective
Prevent customer to reach return_uri before success payment
Jira: #257
2. Description of change
Sec-fetch header is checked to determine whether the request is a user originated operation or not. Created a new helper class request for it. This can be used to add request related helper function in the future.
Reference
HTTP_REFERER header was not present this time. We might need to change the implementation in Magento.
Reference
3. Quality assurance
http://{YOUR_BASE_PATH}/?wc-api=omise_callback&order_id={ORDER_ID}
🔧 Environments: