1
With send support, proxy setup examples should be updated
Source: dani-garcia/vaultwarden#1593 · opened by @swstim
I mentioned this in discussions, but I think it's important enough to post again here:
Now with send support, the [Apache reverse proxy suggested setup]( should be updated.
I have tested and now use the following mod_rewrite config:
This should also be more future proof then specifying a specific path eg /notifications/hub(.*).
_Originally posted by @swstim in
Now with send support, the [Apache reverse proxy suggested setup]( should be updated.
I have tested and now use the following mod_rewrite config:
This should also be more future proof then specifying a specific path eg /notifications/hub(.*).
_Originally posted by @swstim in
No pledges yet. Be the first to back this.
Comments
Similar requests
GitHub repo containing upstream examples for self-hosting
0 votes · 0 comments
Feature Request: User-based Permissions for “Send” Feature
1 vote · 0 comments
Allow /send/ to be exposed on a separate port while keeping Vaultwarden internal
1 vote · 0 comments
Feature Request: User-based Permissions for “Send” Feature
2 votes · 0 comments
Customizable "send" URL
11 votes · 0 comments
No comments yet.