[GH-ISSUE #633] ?noscript creates broken relative links when path prefix is not / #379

Closed
opened 2026-04-08 16:52:29 +03:00 by zhus · 1 comment
Owner

Originally created by @apfelchips on GitHub (Sep 22, 2025).
Original GitHub issue: https://github.com/sigoden/dufs/issues/633

The new ?noscript HTTP GET option breaks when the dufs server is being served / reverse proxied under a subdirectory with the --path-prefix option

Configuration

dufs --bind 127.0.0.1 --port 12345 ~/downloads/ --hidden '.DS_Store,._*' --path-prefix /dufs-downloads/

The generated html doesn't include the prefix-path in the anchor tags:

  <tbody>
    <tr><td><a href="../?noscript">../</a></td><td></td><td></td></tr>
    <tr><td><a href="ExampleDir/?noscript">ExampleDir/</a></td><td>2025-08-30T23:57:03.040Z</td><td>10 items</td></tr>
  </tbody>

The index page loads successfully, but the links to the files and directories result in a 404 error.

Please add the path-prefix to the links on the noscript pages.

Also please consider adding a --noscript flag that changes the behavior to always serve the noscript page by default ( I sometimes use dufs to access content from legacy devices with truly ancient js engines and it would be awesome if they'd just work without having to add the GET parameter )

Log

Screenshots/Media

Environment Information

  • Dufs version: v0.45.0
  • Browser/Webdav info: any
  • OS info: any
  • Proxy server (if any): Apache ProxyPass
Originally created by @apfelchips on GitHub (Sep 22, 2025). Original GitHub issue: https://github.com/sigoden/dufs/issues/633 The new `?noscript` HTTP GET option breaks when the dufs server is being served / reverse proxied under a subdirectory with the `--path-prefix` option **Configuration** <!-- Please specify the Dufs command-line arguments or configuration used. --> ```bash dufs --bind 127.0.0.1 --port 12345 ~/downloads/ --hidden '.DS_Store,._*' --path-prefix /dufs-downloads/ ``` The generated html doesn't include the prefix-path in the anchor tags: ```html <tbody> <tr><td><a href="../?noscript">../</a></td><td></td><td></td></tr> <tr><td><a href="ExampleDir/?noscript">ExampleDir/</a></td><td>2025-08-30T23:57:03.040Z</td><td>10 items</td></tr> </tbody> ``` The index page loads successfully, but the links to the files and directories result in a 404 error. Please add the path-prefix to the links on the noscript pages. Also please consider adding a `--noscript` flag that changes the behavior to always serve the noscript page by default ( I sometimes use dufs to access content from legacy devices with truly ancient js engines and it would be awesome if they'd just work without having to add the GET parameter ) <!-- If the issue is related to authentication/permissions, include auth configurations while concealing sensitive information (e.g., passwords). --> **Log** <!-- Attach relevant log outputs that can help diagnose the issue. --> **Screenshots/Media** <!-- If applicable, add screenshots or videos that help illustrate the issue, especially for WebUI problems. --> **Environment Information** - Dufs version: v0.45.0 - Browser/Webdav info: any - OS info: any - Proxy server (if any): Apache ProxyPass
zhus closed this issue 2026-04-08 16:52:29 +03:00
Author
Owner

@sigoden commented on GitHub (Sep 22, 2025):

The ?noscript works with --path-prefix.
We will not support --noscript flag.

<!-- gh-comment-id:3316303712 --> @sigoden commented on GitHub (Sep 22, 2025): The `?noscript` works with `--path-prefix`. We will not support `--noscript` flag.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sigoden/dufs#379