v2.0.0-preview-4 #2704
Replies: 4 comments
|
Fine |
|
Fantastic |
|
Found an issue with media files:
|
|
I believe there may be a Windows path-normalization bug in FileBrowser Quantum v2.0.0-preview-4 (and 3), specifically in the new source/access-control handling. I am running FileBrowser Quantum natively on Windows with a source located on the E: drive. Authentication succeeds, the source is recognized and indexed, and the administrator account has the correct source scope and all relevant permissions. However, opening the source always results in: 403 access denied When I inspect the corresponding access-control endpoint, it returns: { This makes me suspect that the configured Windows path is being normalized internally to a native path and then passed into a validator intended for virtual/index paths, which rejects backslashes. Environment There is no reverse proxy, Cloudflare, or external-domain involvement. The same issue occurs directly through 127.0.0.1. This is my config.yaml: server: sources: cacheDir: "tmp" database: http: I also tested without createUserDir and with all default source permissions enabled. The behavior did not change. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
2.0.0 Preview update 4
This preview update addresses some migration challenges brought up from the previous discussion. A common migration issue was when there was no database specified in the config. So I have added a
migrateFrom: defaultoption where it preferes the existing environment variables. Considering most config files don't have thedatabaselocation specified and use env vars or defaults, this should make migrations less confusing for most.Please: enable the opt-in analytics in settings > System & Admin, since this is a preview build; doing that at least while running the preview is very helpful to me.
Also I would prefer all issues and comments in the discussion for this release (rather than opening issues)
What's Changed
Full Changelog: v2.0.0-preview-3...v2.0.0-preview-4
This discussion was created from the release v2.0.0-preview-4.
All reactions