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: Sat, 24 Feb 2024 21:12:19 +0100 [thread overview]
Message-ID: <87msrppqos.wl-jch@irif.fr> (raw)
In-Reply-To: <CAHpL4=i0ogpp2PdVnkSgjBDWcRKAsS8=p3z36UbKMcPM0F0zKg@mail.gmail.com>
>> Is your proxy rewriting the paths? Or is it just gluing multiple sites
>> together?
> The latter. I use haproxy with a frontend config that forwards the
> HTTP requests to a backend server based on path rules. Here is an
> example config:
> frontend https
> bind *:443 ssl crt /etc/haproxy/selfsigned.pem crt
> /etc/haproxy/certs.d alpn h2,http/1.1
> mode http
> acl is_path_galene path_beg -i /foo
> use_backend galene if is_path_galene
>
> backend galene
> mode http
> server srv_galene 127.0.0.1:43210
What happens if you add
http-request set-path "%[path,regsub(^/foo/,/)]" if is_path_galene
?
-- Juliusz
next prev parent reply other threads:[~2024-02-24 20:12 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 ` [Galene] " Juliusz Chroboczek
2024-01-18 14:56 ` 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 [this message]
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=87msrppqos.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