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
It is currently impossible to activate the extensionfor all files
We would like to configure the extension to secure all files in the secure directory. We tried to set the setting "basic.securedFiletypes" to ".*" which would match every extension, however this breaks the frontend (regex matches characters outside of the href= attribute). Then only setting that worked was [^'"]+ (which is clearly a hack, but matches everything until the closing " of the href attribute).
To Reproduce
Steps to reproduce the behavior:
Install Secure Downloads 3.0.0
Configure basic.securedFiletypes with .*
Open page with secured file on it
open secured file
Expected behavior
The secured file should be opened.
The page with the secured link should be rendered correctly.
Additional context
One setting, which we also tried, was .*? - this would match so few characters as possible (lazy) - but then we could not open the secured file, we got an error "Hash invalid! Access denied!"
The text was updated successfully, but these errors were encountered:
It is currently impossible to activate the extensionfor all files
We would like to configure the extension to secure all files in the secure directory. We tried to set the setting "basic.securedFiletypes" to ".*" which would match every extension, however this breaks the frontend (regex matches characters outside of the href= attribute). Then only setting that worked was [^'"]+ (which is clearly a hack, but matches everything until the closing " of the href attribute).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Additional context
One setting, which we also tried, was .*? - this would match so few characters as possible (lazy) - but then we could not open the secured file, we got an error "Hash invalid! Access denied!"
The text was updated successfully, but these errors were encountered: