docs: A few fixes, one more example (#164)

- Change wildcard certs patterns from h3 to h2 header
- Clean up `encode.md` a bit
- Add TOC entry for `handle_response`
- Add response matcher docs for `handle_response` (copied from `encode.md`)
- Add example for `handle_response` for handling by status code

src/docs/markdown/caddyfile/directives/encode.md

@@ -30,7 +30,7 @@ encode [<matcher>] <formats...> {
 - **gzip** enables Gzip compression, optionally at the specified level.
 - **zstd** enables Zstandard compression.
 - **minimum_length** the minimum number of bytes a response should have to be encoded (default: 512).
-- **match** is a [Response matcher](#responsematcher). Only matching Responses are encoded. The default looks like this:
+- **match** is a [response matcher](#response-matcher). Only matching responses are encoded. The default looks like this:
 
   ```caddy-d
   match {
@@ -60,7 +60,7 @@ By HTTP status code.
 
 ### header
 
-See Request matcher [header](/docs/caddyfile/matchers#header).
+See the [header](/docs/caddyfile/matchers#header) request matcher for the supported syntax.
 
 ## Examples
 

src/docs/markdown/caddyfile/directives/reverse_proxy.md

@@ -16,6 +16,7 @@ Proxies requests to one or more backends with configurable transport, load balan
 - [Transports](#transports)
   - [The `http` transport](#the-http-transport)
   - [The `fastcgi` tranport](#the-fastcgi-transport)
+- [Intercepting responses](#intercepting-responses)
 - [Examples](#examples)
 
 
@@ -259,11 +260,26 @@ transport fastcgi {
 
 The reverse proxy can be configured to intercept responses from the backend. To facilitate this, response matchers can be defined (similar to the syntax for request matchers) and the first matching `handle_response` route will be invoked. When this happens, the response from the backend is not written to the client, and the configured `handle_response` route will be executed instead, and it is up to that route to write a response.
 
-- **@name** is the name of a response matcher. As long as each response matcher has a unique name, multiple matchers can be defined. A response can be matched on the status code and presence or value of a response header.
+- **@name** is the name of a [response matcher](#response-matcher). As long as each response matcher has a unique name, multiple matchers can be defined. A response can be matched on the status code and presence or value of a response header.
 - **handle_response** defines the route to execute when matched by the given matcher (or, if a matcher is omitted, all responses). The first matching block will be applied. Inside a `handle_response` block, any other [directives](/docs/caddyfile/directives) can be used.
 
+#### Response matcher
 
+**Response matchers** can be used to filter (or classify) responses by specific criteria.
 
+##### status
+
+```caddy-d
+status <code...>
+```
+
+By HTTP status code.
+
+- **&lt;code...&gt;** is a list of HTTP status codes. Special cases are `2xx`, `3xx`, ... which match against all status codes in the range of 200-299, 300-399, ... respectively
+
+##### header
+
+See the [header](/docs/caddyfile/matchers#header) request matcher for the supported syntax.
 
 ## Examples
 
@@ -333,3 +349,16 @@ reverse_proxy localhost:8080 {
 	}
 }
 ```
+
+Custom error page for errors from upstream:
+
+```
+reverse_proxy localhost:8080 {
+	@error status 500 503
+	handle_response @error {
+		root    * /path/to/error/pages
+		rewrite   /{http.reverse_proxy.status_code}.html
+		file_server
+	}
+}
+```

src/docs/markdown/caddyfile/patterns.md

@@ -128,7 +128,7 @@ redir /remove/ /remove
 Using a redirect, the client will have to re-issue the request, enforcing a single acceptable URI for a resource.
 
 
-### Wildcard certificates
+## Wildcard certificates
 
 If you need to serve multiple subdomains with the same wildcard certificate, the best way to handle them is with a Caddyfile like this, making use of the [`handle`](/docs/caddyfile/directives/handle) directive and [`host`](/docs/caddyfile/matchers#host) matchers: