timmy/k3s
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: ensure correct Content-Type for well-known endpoint

Browse Source
This commit is contained in:
Timmy
2026-04-02 15:28:55 +08:00
parent 11af6bf3f2
commit d2ec622f5a
1 changed files with 11 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
apps/vaultwarden/manifests/00-well-known-configmap.yaml
View File

@@ -8,9 +8,18 @@ data:
listen 8080; listen 8080;
server_name _; server_name _;
# Well-known endpoint for Bitwarden clients # Well-known endpoint for Bitwarden clients (multiple variations)
location /.well-known/bitwarden/ { location /.well-known/bitwarden/ {
add_header Content-Type application/json; default_type application/json;
add_header Content-Type application/json always;
add_header Access-Control-Allow-Origin * always;
return 200 '{"object":"bitwarden-bitwarden-host","api":"https://vaultwarden.lotimmy.com"}';
}
location = /.well-known/bitwarden {
default_type application/json;
add_header Content-Type application/json always;
add_header Access-Control-Allow-Origin * always;
return 200 '{"object":"bitwarden-bitwarden-host","api":"https://vaultwarden.lotimmy.com"}'; return 200 '{"object":"bitwarden-bitwarden-host","api":"https://vaultwarden.lotimmy.com"}';
} }