Allow configuring the User-Agent sent to Nextcloud - #723
Conversation
Some deployments front Nextcloud with proxies/WAFs that filter requests based on User-Agent, so the push daemon needs a way to send a custom one for the requests it makes to the Nextcloud instance (including credential verification). Adds a USER_AGENT env var / --user-agent flag, following the same config plumbing as ALLOW_SELF_SIGNED. Signed-off-by: Matthias Sauer <sauerm@strato.de>
fbecb1f to
7a12c6f
Compare
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
2 participants
Some deployments front Nextcloud with proxies/WAFs that filter requests based on User-Agent, so the push daemon needs a way to send a custom one for the requests it makes to the Nextcloud instance (including credential verification). Adds a USER_AGENT env var / --user-agent flag, following the same config plumbing as ALLOW_SELF_SIGNED.
🤖 AI (if applicable)