This is not needed for reverse proxies:
Require all granted
On Wed, Jan 4, 2023 at 6:26 PM Florian Schwalm wrote:
> Nice, thank you for sharing the final result :)
>
> Am 5. Januar 2023 00:08:07 MEZ schrieb Jan Kohnert <
> nospam001-li...@jan-kohnert.de>:
>>
>> Am Mittwoch, 28. Dezember 2022,
Nice, thank you for sharing the final result :)
Am 5. Januar 2023 00:08:07 MEZ schrieb Jan Kohnert
:
>Am Mittwoch, 28. Dezember 2022, 11:53:58 CET schrieb Jan Kohnert:
>> The config reads as:
>>
>> ---
>> RequestHeader add X
Am Mittwoch, 28. Dezember 2022, 11:53:58 CET schrieb Jan Kohnert:
> The config reads as:
>
> ---
> RequestHeader add X-Forwarded-Ssl on
> RequestHeader set X-Forwarded-Proto "https"
>
>
> Require all granted
>
>
>
>
Am Dienstag, 27. Dezember 2022, 22:47:53 CET schrieb Florian Schwalm:
> > Reading through the report, this bug probably hit me, too. GitLab is a
> > Ruby-on-rails application using a Puma Webserver internally, connected to
> > Apache all over UNIX-sockets; this cable-stuff mentioned in the report i
> As far as I understood, the "P" flag implies "L"
True, so that part of the docs seems redundant
> Reading through the report, this bug probably hit me, too. GitLab is a Ruby-
on-rails application using a Puma Webserver internally, connected to Apache
all over UNIX-sockets; this cable-stuff men
Am Dienstag, 27. Dezember 2022, 20:32:28 CET schrieb Florian Schwalm:
> As far as I understand Gitlab sends a HTTP GET request first to ask the
> backend to upgrade to websockets. By always proxying /-/cable to ws right
> away you prevent that first upgrade request from succeeding which is
> probab
As far as I understand Gitlab sends a HTTP GET request first to ask the backend
to upgrade to websockets. By always proxying /-/cable to ws right away you
prevent that first upgrade request from succeeding which is probably where the
new error message originates. That's why the mod_proxy_wstunne
Hi,
Am Sonntag, 25. Dezember 2022, 10:56:07 CET schrieb Florian Schwalm:
> Specifying ws instead of http in the RewriteRule should be good.
thanks for the reply! I did that, that's how I got the log error. At first,
the wstunnel-module was not installed; but installing (and loading) it did not
Specifying ws instead of http in the RewriteRule should be good.
> If you are using a DSO version of mod_proxy, make
sure the proxy submodules are included in the configuration using LoadModule.
Did you explicitly load the mod_proxy_wstunnel module as is mentioned in the
error message? The erro
Hello everyone,
I've set up a GitLab instance running behind an Apache HTTP-Server acting a
proxy. GitLab officially only supports NGINX as a proxy, but since my Apache
also serves different VirtualHosts, I'd rather keep the setup I have instead
of setting up another WebServer.
According to [1
10 matches
Mail list logo
