You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(objectql,rest): single-item meta reads must revalidate (no max-age=3600) (#2264)
GET /api/v1/meta/object/:name served `Cache-Control: public, max-age, max-age=3600`. A 1h TTL let browsers/CDNs serve a stale object schema without revalidating (the AI-build "New" form kept rendering pre-publish fields), and the directive list collided with the appended max-age into a malformed triple.
getMetaItemCached now returns directives ['private','no-cache'] with no maxAge, so the ETag validator (already correct on publish) gates freshness — a cheap 304 when unchanged, fresh data the moment a publish bumps the ETag. The REST header builder strips the bare max-age placeholder before appending the real value, so a maxAge emits once as a well-formed max-age=N. 'private' keeps per-tenant metadata out of shared caches.
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
0 commit comments