You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks to the new Cache tab I added to debugbar, i've realised that VersionProvider is always setting the cache due to an invalid cache key (somehow it's not throwing an exception i guess the adapter silently rewrites the key and therefore it's never found when using get)
as per psr 6
According to PSR-6 the following characters could be used in a valid cache key; A-Z, a-z, 0-9, _, and .. Some characters are forbidden like: {}()/@:. If you use any of the forbidden characters you will get an exception. Other characters (like -) are not forbidden nor valid. It is up to the implementation if they support that character or not.
current key includes / and \ due to the path being used
Affected Version
4/5
Description
Thanks to the new Cache tab I added to debugbar, i've realised that VersionProvider is always setting the cache due to an invalid cache key (somehow it's not throwing an exception i guess the adapter silently rewrites the key and therefore it's never found when using get)
as per psr 6
According to PSR-6 the following characters could be used in a valid cache key; A-Z, a-z, 0-9, _, and .. Some characters are forbidden like: {}()/@:. If you use any of the forbidden characters you will get an exception. Other characters (like -) are not forbidden nor valid. It is up to the implementation if they support that character or not.
current key includes / and \ due to the path being used
Steps to Reproduce
PRs
The text was updated successfully, but these errors were encountered: