avoid opcache_invalidate to result in ErrorException #244
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
calling opcache_invalidate will result in ErrorException (Zend OPcache API is restricted by "restrict_api") if opcache.restrict_api is not empty and script is used outside of allowed path. I suggest that there is check which makes sure that function is not called unless opcache.restrict_api is empty - for compatibility with shared webhostings where this configuration property might be common.
uwetews
added a commit
that referenced
this pull request
Jul 18, 2016
…cache.restrict_api is not empty #244
|
I committed this as a patch as opcache_invalidate is used also in several other locations. |
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.
calling opcache_invalidate will result in ErrorException (Zend OPcache API is restricted by "restrict_api") if opcache.restrict_api is not empty and script is used outside of allowed path. I suggest that there is check which makes sure that function is not called unless opcache.restrict_api is empty - for compatibility with shared webhostings where this configuration property might be common.