caddy/modules
Jens-Uwe Mager 2bb2ecc549
reverseproxy: Change errors writing the response to warning. (#6532)
Most of the errors that can be seen here are write errors due to clients
aborting the request from their side. Often seen ones include:

	* writing: ... write: broken pipe
	* writing: ... connection timed out
	* writing: http2: stream closed
	* writing: timeout...
	* writing: h3 error...

Most of these errors are beyond of the control of caddy on the client side,
probably nothing can be done on the server side. It still warrants
researching when these errors occur very often, so a change in level from
error to warn is better here to not polute the logs with errors in the
normal case.
2024-08-21 11:39:20 -06:00
..
caddyevents events: Getters for event info (close #6377) 2024-06-06 07:11:28 -06:00
caddyfs fix a typo (#6333) 2024-05-21 18:41:41 -04:00
caddyhttp reverseproxy: Change errors writing the response to warning. (#6532) 2024-08-21 11:39:20 -06:00
caddypki acmeserver: Add sign_with_root for Caddyfile (#6345) 2024-05-27 20:06:54 -04:00
caddytls matchers: fix a regression in #6480 (#6510) 2024-08-12 10:01:09 +03:00
filestorage caddyfile: Normalize & flatten all unmarshalers (#6037) 2024-01-23 19:36:59 -05:00
logging logging: set file mode when the file already exist (#6391) 2024-06-12 15:17:46 -06:00
metrics caddyfile: Normalize & flatten all unmarshalers (#6037) 2024-01-23 19:36:59 -05:00
standard filesystem: Globally declared filesystems, fs directive (#5833) 2024-01-13 20:12:43 +00:00