GitFlare を日本語でご利用いただけます。 日本語で見る · GitFlare 提供简体中文站点。 查看简体中文 ·

Product changelog

Customer-visible changes to the edge platform.

2026-09-12 — Tokyo NRT capacity and origin HTTP/2 keepalives

We added a second cache ring in NRT-1 and turned on HTTP/2 keepalives to origins by default for Pro and Enterprise zones in Japan. Idle origin connections now last 850 seconds, which cuts TLS handshakes on the origin path during weekday peaks.

Opt out per zone if your origin still speaks HTTP/1.1 only:

$ gitflare origin update checkout.example.com --http2-keepalive=off
$ gitflare origin get checkout.example.com --json

2026-08-03 — WAF managed ruleset 2026.8

Ruleset 2026.8 raises the default anomaly score for JSON bodies on /api/* and adds a managed rule for oversized GraphQL batching. Existing custom exceptions are unchanged.

$ curl -sS https://api.gitflare.net/v1/waf/rulesets/managed \
  -H "Authorization: Bearer $GITFLARE_API_TOKEN" | jq .version

2026-07-18 — Workers isolate reuse on Pro and Enterprise

Isolates on paid plans now stay warm for up to 30 minutes of idleness. Cold starts on Tokyo traffic dropped from p95 42ms to 11ms in our canary week.

export default {
  async fetch(req, env, ctx) {
    ctx.waitUntil(env.METRICS.write({ colo: req.cf.colo, t: Date.now() }));
    return env.APP.fetch(req);
  }
};

2026-06-02 — Edge KV list pagination

GET /kv/namespaces/:id/keys now returns cursor instead of silently truncating at 1,000 keys. SDKs older than 1.19 still work; they ignore the new field.

$ curl -sS "https://api.gitflare.net/v1/kv/namespaces/$NS/keys?limit=100" \
  -H "Authorization: Bearer $GITFLARE_API_TOKEN"

2026-05-11 — Automatic TLS 1.3-only extra hostnames

Hostnames added through the dashboard now advertise TLS 1.3 only. Legacy 1.2 remains available as an origin setting for old scanners that still expect it.

$ gitflare hostname add www.example.com --tls=1.3
$ gitflare hostname ssl www.example.com

2026-04-09 — CLI deploy --dry-run

gitflare deploy --dry-run uploads the bundle to a staging isolate and prints the scheduled colo list without shifting production traffic.

$ gitflare deploy --name checkout-api --edge nearest --dry-run

2026-03-20 — Status page JSON

The public status page now exposes a machine-readable feed for runbooks.

$ curl -sS https://gitflare.net/status.json | jq .components

2026-02-14 — Cache purge by prefix

Prefix purge is generally available. A single call can drop /assets/* without enumerating objects.

$ gitflare cache purge --zone example.com --prefix /assets/