-
Notifications
You must be signed in to change notification settings - Fork 301
Open
Description
Environment
- FileBrowser Quantum:
v1.3.1-beta - Docker image:
gtstef/filebrowser:1.3.1-beta-slim - Reverse proxy: Nginx (HTTPS)
- Also reproduced when accessing container directly (
http://127.0.0.1:8080) without proxy path changes.
Steps to Reproduce
- Upload a simple HTML file (example below).
- Create a public share link for that file.
- Open the share page:
/public/share/<hash>. - Observe the built-in viewer area.
- Click the top-right menu (
...) ->Open File.
Example HTML:
<!doctype html>
<meta charset="utf-8">
<h1>OK</h1>
<p>Quantum preview test</p>
Actual Behavior
- Share page viewer is blank/empty.
- Open File opens /public/api/resources/download?file=%2F&hash=<hash>&inline=true and renders HTML correctly in browser.
Expected Behavior
- The share page viewer should display the HTML content (or at least show source consistently), instead of a blank panel.
Diagnostic Notes
- GET /public/api/resources?path=%2F&hash=<hash>&content=true returns 200 with:
- type: "text/html"
- content: "<!doctype html>..."
- hasPreview: false
- GET /public/api/resources/download?file=%2F&hash=<hash>&inline=true returns 200 and renders correctly.
- Same behavior through Nginx and directly on container, so this does not appear to be a reverse-proxy issue.
- Browser console showed no blocking JS error related to this rendering path.
Impact
Users sharing HTML files see a blank viewer and may think the share is broken, even though inline open works.Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels