v0.16.4

Update changelog for 0.16.4.

v0.16.3

Update `release.yml` to use 1.87

v0.16.2

Merge pull request #565 from fastly/release-0.16.2

Release v0.16.2

v0.16.1

Viceroy 0.16.1 release

v0.16.0

A few tweaks to support more HTTP functionality and bring the server closer to functional parity with the Compute platform

---

💡 Rudimentary HTTP 103 support

Courtesy of @bahamat in #550

The server will now catch, log, and drop 103s so that they are displayed in the output, but they will not be sent to the client due to limitations in the HTTP library we use. The end result is that developers can test 103 support when developing their Compute services, and see that the 103s were generated and transmitted out of the service, but they will be elided from the response stream sent back to the client. The client will still receive the final response.

💿 Core Cache consistency

Try saying that three times... thanks @cceckman! (#552)

The Compute platform, at the moment, only returns FOUND if within the USABLE period (in HTTP semantics, "fresh" or "stale-while-revalidate"). Unfortunately, SDKs rely on this property, and check FOUND or USABLE variously; sometimes (e.g. in Rust), this results in a FOUND-but-not-USABLE result being returned. This change updates the local testing server to match this behaviour, only returning FOUND if the object is USABLE.

🔧 Set HTTP framing headers manually

Added by @kailan in #551

Developers can now use the set_framing_headers_mode SDK method to indicate that they would like to set framing headers (Content-Length and Transfer-Encoding) on requests and responses themselves, instead of the platform handling it for them. This is helpful when streaming files to a client where the size is known ahead of time. Previously, using this method would throw an error, halting execution of the request. Similar to the behaviour of Compute in production, the content of the headers will be validated and if it is invalid, the server will fall back to automatic framing headers.

---

If you use the Fastly CLI, you should see this functionality available later today. If using directly, run cargo install viceroy to update to the latest version. Happy hacking!

Full Changelog: v0.15.0...v0.16.0

v0.15.0

Release v0.15.0

- Update lock files
- Update changelog

v0.14.4

Prepare release v0.14.4

v0.14.3

Prepare release v0.14.3

v0.14.2

Update changelog, upgrade Rust, update resolver, and update lockfiles

With wasmtime v28, we can safely:
- Update lockfiles, which requires an `spdx` upgrade
- Upgrade Rust to 1.85, is required by `spdx`
- Use the version-aware `resolver = "3"`, which is supported in 1.85.

v0.14.1

Note: this version was not published to crates.io.

We recommend using v0.14.2 rather than this release.