Main #67
Open
Main #67
Conversation
This file contains 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 commit addresses an issue where the existing codebase was limited to sending messages over HTTP and MQTT protocols, failing to properly handle HTTPS requests due to missing implementation. With the introduction of new modifications, the system is now fully equipped to send messages securely over HTTPS, alongside the pre-existing HTTP and MQTT capabilities.
Key improvements include:
Implementation of SSL/TLS encryption for message transmission, ensuring secure communication over HTTPS.
Integration of HTTPS protocol handling within the messaging function, allowing for seamless switching between HTTP, HTTPS, and MQTT based on the URI scheme.
Note
Please double-check whether the code works for htpp and mqqt.