Update LTI_Message_Launch.php get_public_key method #85
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
I can't say exactly when this started happening but all of my instances of LTI connection via Moodle 4.1.4 failed with PHP Warning: file_get_contents(https://moodletesting.tiltroleplay.com/mod/lti/certs.php): failed to open stream: HTTP request failed! HTTP/1.1 403 Forbidden. In case anyone else runs into this issue either edit this method yourself or employ CURL to do same but if in WP environment can't always rely on CURL being enabled or as an option by host.
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.
I can't say exactly when this started happening but all of my instances of LTI connection via Moodle 4.1.4 failed with PHP Warning: file_get_contents(https://moodletesting.tiltroleplay.com/mod/lti/certs.php): failed to open stream: HTTP request failed! HTTP/1.1 403 Forbidden. In case anyone else runs into this issue either edit this method yourself or employ CURL to do same but if in WP environment can't always rely on CURL being enabled or as an option by host.