-
Notifications
You must be signed in to change notification settings - Fork 12k
An asset cannot be read from a location outside the project configuration 1.6.0 #8783
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Was working on 1.6.4, but since the new 1.6.5 it is failing again! |
Not sure if this is related but it is a somewhat similar #8613 (comment) |
Same here. tried 1.6.4, 1.6.5, 1.6.6, 1.6.7, 1.6.8, 1.7.3 :( |
Same here on 1.70, worked with 1.50
|
any workarounds for this? |
Closing as this is working as intended. Files cannot be read outside of the workspace root directory as there is also a potential security concern. Especially now that deploying the application is possible via a |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Versions
Repro steps
Observed behavior
Load file from an external folder now fails because of this check :
An asset cannot be read from a location outside the project
Introduced by the PR:
64c6031#diff-9eb0a75e499bdadd44d6dc62218812b8
could be possible introduce a parameter configuration as allowOutsideOutDir but for reading? something like :
It could be false by default and be enabled by the user only when he knows the security risk behind this kind of decision.
Side note the warning message could be improved indicating the assets failing
Desired behavior
Mention any other details that might be useful (optional)
If the idea above are ok for the project I could create a PR
The text was updated successfully, but these errors were encountered: