fix: update ReveSMS provider URIs to use HTTP instead of HTTPS #8
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request updates the ReveSMS integration to use the new API endpoint and modifies how requests are sent to comply with the provider’s requirements. The main changes include switching from the old
smpp.revesms.comendpoint toapismpp.revesms.comand changing the request method for sending SMS messages from GET to POST with form parameters.Provider endpoint changes:
https://smpp.revesms.comtohttp://apismpp.revesms.comin configuration, provider code, and tests. [1] [2] [3] [4]Request method and payload changes:
ReveSmsProviderfrom using a GET request with query parameters to a POST request with form parameters, matching the new API requirements.