Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: Francis Bolduc <fbolduc@gmail.com>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Behind reverse proxy, not at the root
Date: Thu, 18 Jan 2024 12:08:31 +0100	[thread overview]
Message-ID: <87le8mzyog.wl-jch@irif.fr> (raw)
In-Reply-To: <CAHpL4=igK9LLzyxFd76FEZ4cWY+gG_x5Q_BsyA3YJrafGgpp9w@mail.gmail.com>

> Each application has its own path. For example, I have a file server
> located at https://myhost.com/files and a streaming service at
> https://myhost.com/stream.
> 
> Each application has some configuration option to tell it that they
> are not located at the root, but rather under some path like /files or
> /stream.
> 
> However, I've not found how to do that with Galene. Is there an option
> to this that I missed?

No, it's not currently supported.  It wouldn't be too difficult to do, as
usual it's testing that's a pain.  (Galene has a fairly extensive set of
units tests for low-level functionality, but there are no high-level tests
of the server as a whole, so I need to test manually with each release.
So the more configuration options we add, the more testing I need to do.)

I'll think it over, but no promises.

(Off topic, but are you aware that by doing that you defeat sandboxing?
HTML5 performs sandboxing on a per-origin basis, not a per-subtree basis,
so when multiple applications are running on the same domain, a security
flaw in just one of the applications will allow exploitation of all of
them.  For example, an XSS vulnerability in your files application will
allow an attacker to exfiltrate Galene's passwords.  The more secure
configuration is to use a different hostname for each application,
files.example.org, stream.example.org, etc.)


-- Juliusz

  reply	other threads:[~2024-01-18 11:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 23:40 [Galene] " Francis Bolduc
2024-01-18 11:08 ` Juliusz Chroboczek [this message]
2024-01-18 14:56   ` [Galene] " Francis Bolduc
2024-02-24 11:49 ` Juliusz Chroboczek
2024-02-24 14:34   ` Francis Bolduc
2024-02-24 18:27     ` Francis Bolduc
2024-02-24 18:44       ` Juliusz Chroboczek
2024-02-24 18:56         ` Francis Bolduc
2024-02-24 20:12           ` Juliusz Chroboczek
2024-02-24 21:28             ` Francis Bolduc
2024-02-24 22:16               ` Juliusz Chroboczek
2024-02-24 22:19                 ` Francis Bolduc
2024-02-24 22:49                   ` Juliusz Chroboczek
2024-02-25  0:51                     ` Francis Bolduc
2024-02-25 11:10                       ` Juliusz Chroboczek
2024-03-03 15:20                         ` Juliusz Chroboczek
2024-03-03 15:30                           ` Dianne Skoll
     [not found]                           ` <170947981403.1000.17286547855683116289@gauss.local>
2024-03-03 15:52                             ` Juliusz Chroboczek
2024-03-03 16:04                             ` Dirk-Willem van Gulik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87le8mzyog.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=fbolduc@gmail.com \
    --cc=galene@lists.galene.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox