Lukas Wagner 6d4c115f05 notify: webhook: gotify: set Content-Length header ... To quote from RFC 9110 [1]: A user agent SHOULD send Content-Length in a request when the method defines a meaning for enclosed content and it is not sending Transfer-Encoding. For example, a user agent normally sends Content-Length in a POST request even when the value is 0 (indicating empty content). A user agent SHOULD NOT send a Content-Length header field when the request message does not contain content and the method semantics do not anticipate such data. It seemed like our HTTP client lib did not set the header automatically, which is why we should do it manually. While most services seemed to have worked fine without setting the header, some Microsoft services seem to require it to accept the webhook request [2]. [1] https://datatracker.ietf.org/doc/html/rfc9110#name-content-length [2] https://forum.proxmox.com/threads/158827 Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>		2025-03-25 19:37:37 +01:00
..
debian	notify: bump d/control	2025-02-19 13:02:00 +01:00
src	notify: webhook: gotify: set Content-Length header	2025-03-25 19:37:37 +01:00
Cargo.toml	notify: bump to 0.5.3-1	2025-02-19 13:00:56 +01:00