head	1.1;
access;
symbols
	pkgsrc-2026Q1:1.1.0.30
	pkgsrc-2026Q1-base:1.1
	pkgsrc-2025Q4:1.1.0.28
	pkgsrc-2025Q4-base:1.1
	pkgsrc-2025Q3:1.1.0.26
	pkgsrc-2025Q3-base:1.1
	pkgsrc-2025Q2:1.1.0.24
	pkgsrc-2025Q2-base:1.1
	pkgsrc-2025Q1:1.1.0.22
	pkgsrc-2025Q1-base:1.1
	pkgsrc-2024Q4:1.1.0.20
	pkgsrc-2024Q4-base:1.1
	pkgsrc-2024Q3:1.1.0.18
	pkgsrc-2024Q3-base:1.1
	pkgsrc-2024Q2:1.1.0.16
	pkgsrc-2024Q2-base:1.1
	pkgsrc-2024Q1:1.1.0.14
	pkgsrc-2024Q1-base:1.1
	pkgsrc-2023Q4:1.1.0.12
	pkgsrc-2023Q4-base:1.1
	pkgsrc-2023Q3:1.1.0.10
	pkgsrc-2023Q3-base:1.1
	pkgsrc-2023Q2:1.1.0.8
	pkgsrc-2023Q2-base:1.1
	pkgsrc-2023Q1:1.1.0.6
	pkgsrc-2023Q1-base:1.1
	pkgsrc-2022Q4:1.1.0.4
	pkgsrc-2022Q4-base:1.1
	pkgsrc-2022Q3:1.1.0.2
	pkgsrc-2022Q3-base:1.1;
locks; strict;
comment	@# @;


1.1
date	2022.08.17.15.44.16;	author hauke;	state Exp;
branches;
next	;
commitid	UDdA1QiTGs10ofQD;


desc
@@


1.1
log
@Vaultwarden is a Bitwarden server API implementation written in Rust,
compatible with upstream Bitwarden password manager clients.

It is well-suited for self-hosted deployment, where running the
official resource-heavy service might not be ideal.
@
text
@# $NetBSD$

# Apache 2.4 configuration snippet for running vaultwarden behind a
# reverse proxy.
#
# The location does not have a trailing slash, since the Bitwarden
# browser client will strip it. The corresponding vaultwarden.env
# DOMAIN setting is supposed to hold the server's hostname, but not
# the path.

<Location "/bitwarden">

    # WebSocket notifications
    RewriteEngine On
    RewriteCond %{HTTP:Upgrade} websocket [NC]
    RewriteCond %{HTTP:Connection} upgrade [NC]
    RewriteRule ^/?(.*) "ws://localhost:3012/$1" [P,L]

    ProxyPass "http://localhost:8000"
    ProxyPreserveHost On
    RequestHeader set X-Real-IP %{REMOTE_ADDR}s
</Location>
@