# Version 22.6
This is the second release of the version 22 release cycle. Version 22 will be "finalized" in the December long-term support version release.
# What to know
More details in the Changelog (opens new window). Notable new or breaking features, and what to upgrade...
# Automatic TLS setup in
The Sanic server can automatically setup a TLS certificate using either mkcert (opens new window) or trustme (opens new window). This certificate will enable
https://localhost (or another local address) for local development environments. You must install either
trustme on your own for this to work.
$ sanic path.to.server:app --auto-tls --debug
This feature is not available when running in
ASGI mode, or in
PRODUCTION mode. When running Sanic in production, you should be using a real TLS certificate either purchased through a legitimate vendor, or using Let's Encrypt (opens new window).
# HTTP/3 Server 🚀
In June 2022, the IETF finalized and published RFC 9114 (opens new window), the specification for HTTP/3. In short, HTTP/3 is a very different protocol than HTTP/1.1 and HTTP/2 because it implements HTTP over UDP instead of TCP. The new HTTP protocol promises faster webpage load times and solving some of the problems of the older standards. You are encouraged to read more about (opens new window) this new web technology. You likely will need to install a capable client (opens new window) as traditional tooling will not work.
Sanic server offers HTTP/3 support using aioquic (opens new window). This must be installed:
pip install sanic aioquic
pip install sanic[http3]
To start HTTP/3, you must explicitly request it when running your application.
$ sanic path.to.server:app --http=3
$ sanic path.to.server:app -3
To run both an HTTP/3 and HTTP/1.1 server simultaneously, you can use application multi-serve introduced in v22.3.
$ sanic path.to.server:app --http=3 --http=1
$ sanic path.to.server:app -3 -1
app.prepre(version=3) app.prepre(version=1) Sanic.serve()
Because HTTP/3 requires TLS, you cannot start a HTTP/3 server without a TLS certificate. You should set it up yourself or use
mkcert if in
DEBUG mode. Currently, automatic TLS setup for HTTP/3 is not compatible with
👶 This feature is being released as an EARLY RELEASE FEATURE. It is not yet fully compliant with the HTTP/3 specification, lacking some features like websockets (opens new window), webtransport (opens new window), and push responses (opens new window). Instead the intent of this release is to bring the existing HTTP request/response cycle towards feature parity with HTTP/3. Over the next several releases, more HTTP/3 features will be added and the API for it finalized.
# Consistent exception naming
Some of the Sanic exceptions have been renamed to be more compliant with standard HTTP response names.
All old names have been aliased and will remain backwards compatible.
# Current request getter
Similar to the API to access an application (
Sanic.get_app()), there is a new method for retrieving the current request when outside of a request handler.
from sanic import Request Request.get_current()
# Improved API support for setting cache control headers
file response helper has some added parameters to make it easier to handle setting of the Cache-Control (opens new window) header.
file( ..., last_modified=..., max_age=..., no_store=..., )
Just like Sanic supports globally setting a custom
dumps, you can now set a global custom
from orjson import loads app = Sanic("Test", loads=loads)
# Deprecations and Removals
- REMOVED - Applications may no longer opt-out of the application registry
- REMOVED - Custom exception handlers will no longer run after some part of an exception has been sent
- REMOVED - Fallback error formats cannot be set on the
ErrorHandlerand must only be set in the
- REMOVED - Setting a custom
LOGOfor startup is no longer allowed
- REMOVED - The old
streamresponse convenience method has been removed
- REMOVED -
AsyncServer.initis removed and no longer an alias of
# Thank you
Thank you to everyone that participated in this release: 👏
@ahopkins (opens new window) @amitay87 (opens new window) @ashleysommer (opens new window) @azimovMichael (opens new window) @ChihweiLHBird (opens new window) @kijk2869 (opens new window) @prryplatypus (opens new window) @SaidBySolo (opens new window) @sjsadowski (opens new window) @timmo001 (opens new window) @zozzz (opens new window)
If you enjoy the project, please consider contributing. Of course we love code contributions, but we also love contributions in any form. Consider writing some documentation, showing off use cases, joining conversations and making your voice known, and if you are able: financial contributions (opens new window).