Hi Boyuan, On Di, 2016-07-19 at 09:55 +0800, Boyuan Yang wrote: > Source: mini-buildd > Version: 1.0.12 > Severity: normal
(...) > 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. fwiw, there is an example in mini-buildd /usr/share/doc/mini-buildd/examples/apache-ssl-proxy.conf which does "work for me" (albeit a somewhat different use case, afaiu). > The problem is there are *always* some resource files failing with > 404. The (...) > something else, and failed to be converted by mod_rewrite. That's a little over my head for now ;). I guess I need some more details about your configuration, and what resources actually fail. > May consider setting up an option for such situation, just as what > gogs and > some other web applications do. What do you mean exactly here? Is there some django option to do just that? Thanks! S
