On Sunday, September 6, 2015 at 9:55:44 PM UTC, Cédric Krier wrote:
>
> On 2015-09-06 13:28, Christoph Larsen wrote:
> > Dear All,
> >
> > I have been trying for a few days to make the SAO webclient run in a
> > sub-URI behind an Nginx reverse proxy.
> > The trytond_instance is running in one FreeBSD jail; Nginx as reverse
> proxy
> > in another.
> >
> > I want to run the trytoind_instance in a sub-URI and avoid the
> disturbing
> > appearance of the /sao directory listing that usually comes up, if I
> forget
> > to append "/sao" to the request. I did this:
> >
> > location /trytond_instance {
> > proxy_pass https://trytond.jail.vlan:8050;
> > proxy_redirect https://trytond.jail.vlan:8050/ /trytond_instance/;
> > }
> >
> > Essentially, this should make the trytond_instance available in
> > www.my.domain/trytond_instance, instead of running the instance via a
> > subdomain, e.g. trytond_instance.my.domain.
> > That's easier on SSL certificates and a cleaner way to handle domains,
> IMHO.
> > The above does not work, or rather gives me a barebone, unformatted SAO
> > login screen without any static assets (no graphics, scripts, etc.)
> >
> > This one seems to work:
> >
> > location /trytond_instance {
> > proxy_pass https://trytond.jail.vlan:8050/;
> > proxy_redirect https://trytond.jail.vlan:8050/sao/
> /trytond_instance/;
> > }
> >
> > But then it doesn't: It throws a "Not found" error, and does not display
> > any database in the dropdown.
> > Anyone who has done it? Any hints will be greatly appreciated.
>
> sao is not designed to run at a different path than root for now
> (especially rpc.js)
> Patch is welcomed.
>
> Thanks a lot, Cédric, for letting me know... Much appreciated!
Chris
