Source: mini-buildd Version: 1.0.12 Severity: normal It is clear that mini-buildd web frontend is designed for a standalone site, e.g., "buildd.mywebsite.com/mini_buildd". Mini-buildd works well in such setup.
However, someone may want to setup using reverse proxy. For example, let "https://mywebsite.com/debian/buildd/"; proxy_pass to "http://localhost:8066/";. For apache, `mod_proxy` and `mod_rewrite` may be used to fix URLs in the HTML file. The problem is there are *always* some resource files failing with 404. The path was supposed to be `/debian/buildd/static/...` but ended up with `/static/...`. I guarantee this is *NOT* a mistake in apache2 configuration. No related URL was found in HTML file. I guess they may be loaded with ajax or something else, and failed to be converted by mod_rewrite. May consider setting up an option for such situation, just as what gogs and some other web applications do. -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial'), (100, 'xenial-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-31-generic (SMP w/4 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
