Charles Eckman
Charles Eckman
Support range requests in the cache API. This completes options processing for the "lookup" side, so remove the EXPERIMENTAL flag for those calls. The insert side doesn't handle all the...
Every backend has a "first-byte timeout". This timeout applies to the HTTP response line and response headers. If the client (Compute instance) does not receive all the HTTP headers within...
Every backend has a "first-byte timeout". This timeout applies to the HTTP response line and response headers. If the client (Compute instance) does not receive all the HTTP headers within...
#473 has the last bits of the core cache API that we expect to deliver for now. The [simple cache API](https://docs.rs/fastly/latest/fastly/cache/simple/index.html) should all work. The [core cache API](https://docs.rs/fastly/latest/fastly/cache/core/index.html) is _partly_...
Found via testing in Compute- Viceroy is written in such a way that metadata associated with a `Found` can change; namely, `Found` can get a known length after the fact...
These are rejected in Go as of https://github.com/fastly/compute-sdk-go/pull/165, and in Rust as of PR 5097 in that repository. This is a guest (SDK/runtime) change rather than a host change so...
Every backend has a "first-byte timeout". This timeout applies to the HTTP response line and response headers. If the client (Compute instance) does not receive all the HTTP headers within...
The core cache API allows for cache items to be concurrently streamed to / from the cache. If: - The size of the cached item's body was not provided by...
- Update development instructions to reflect wasm-tools requirement - Remove non-collapsing HTTP cache lookup: not exposed to the JS guest, so it's unused.
We've seen stderr logs from requests with long URLs that report: ``` Exception while initialization of FetchEvent Error: init_request: Buffer length error. Buffer is too long. ``` These seem to...