Operations on WebP Server Documentation

Healthz

Mon, 01 Jan 0001 00:00:00 +0000

Healthz #

There is a /healthz endpoint that can be used to check if the server is up and running. You can use this endpoint for liveness probe.

It returns a 200 status code if the server is up and running.

curl localhost:3333/healthz -v
* Trying 127.0.0.1:3333...
* Connected to localhost (127.0.0.1) port 3333 (#0)
> GET /healthz HTTP/1.1
> Host: localhost:3333
> User-Agent: curl/8.0.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: WebP Server Go
< Date: Fri, 15 Dec 2023 03:16:08 GMT
< Content-Type: text/plain; charset=utf-8
< Content-Length: 34
< Etag: W/"34-1945155614"
<
* Connection #0 to host localhost left intact
WebP Server Go up and running!🥳%

Prefetch

Mon, 01 Jan 0001 00:00:00 +0000

Prefetch #

Prefetch is useful if you’d like to have all your images converted in advance, especially suitable for large amount of images with high traffic volume, using prefetch will convert your images and cache the converted images, hence future requests will not consume computing power.

Start server with prefetch #

Start WebP Server with prefetch enabled will convert all your images to WebP on startup in background, the following things will happen in this mode:

Log Verbosity

Mon, 01 Jan 0001 00:00:00 +0000

Log Verbosity #

You can control log level using --verbosity flag on startup, e,g: ./webp-server --verbosity 0

0 = silent (no log messages)
1 = error (error messages only)
2 = warn (error messages and warnings only)
3 = info (error messages, warnings and normal activity logs)
4 = debug (all info plus additional messages for debugging)