1.29.4

Add the option to reissue certs manually (1.29.4)

1.29.3

• Fixed additional proxying issues.

1.29.2

• Fixed an issue with the proxy servlet on some HTTP methods.

1.29.1

• Fix a Cookie expiry bug in the previous release.

1.29.0

• Management UI!
• Fixed CPU usage issue in Docker.
• Fixed the Certificate Auto Issuer.

1.29.0-pre

Experimental release that has a management UI!

1.28.0

• Moved to Virtual Threads.
• Fixed WebSocket-related thread leaks.

1.27.2

• Fix an issue with some http clients that report a 0-length body (proxy servlet).
• Avoid proxying a GET body as well.

1.27.1

• There is now a WebHook -> WebSocket servlet!

1.26.0

• You can now automatically issue certificates via Let's Encrypt!
  • When enabled, Katana will check every 8 hours for a certificate that is going to expire in 28 days (keeping in-line with Let's Encrypt's recommendations).
  • Right now, only HTTP validation is supported. Which means you cannot use a wildcard domain, and you MUST have Katana able to receive traffic on port 80. Katana will warn you if your server doesn't listen on 80, but it will still attempt validation anyways (for advanced port-routing setups, like in Docker)
• Katana will now hot-reload the SSL certificates if all three files change.
• We had to change how Katana is packaged. Now, when starting Katana, you have to specify the BouncyCastle jar libraries. Provided in the zip file is a start.sh/start.bat which should work for most people.