From 4b3bc5ed7ae10ad5ce1b0972443579da2d43b162 Mon Sep 17 00:00:00 2001 From: Satyam087 Date: Mon, 28 Sep 2026 19:30:20 +0530 Subject: [PATCH] Document use422ForNoDataStatusCode on the feature flags page Follow-up to ERDDAP/erddap#606, which adds the flag. It shapes an HTTP response, so it sits with useHeadersForUrl and enableCors under Web Headers/Configuration. --- docs/server-admin/feature-flags.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/server-admin/feature-flags.md b/docs/server-admin/feature-flags.md index ea8acc4e48..33f5eb830a 100644 --- a/docs/server-admin/feature-flags.md +++ b/docs/server-admin/feature-flags.md @@ -386,6 +386,18 @@ Enables Cross-Origin Resource Sharing (CORS) headers on HTTP responses. | **Long-term Goal** | set as desired | | **History** | Added in 2.26 | +### **use422ForNoDataStatusCode** + +Description +Answers 422 Unprocessable Content instead of 404 when a request names a real dataset but matches no data, for example when a time constraint excludes every row. A client cannot tell the default 404 apart from a dataset that does not exist, and proxies that ban clients after repeated 404s can treat ordinary empty queries as scanning. Staying in the 4xx range keeps `raise_for_status()` and the equivalent checks in other clients firing. A dataset that genuinely is not there still answers 404 either way. + +| Property | Details | +| :---- | :---- | +| **Lifecycle** | Stable | +| **Current Default** | false | +| **Long-term Goal** | set as desired | +| **History** | Added in 2.32.0 | + ## **🔍 Search** ### **useLuceneSearchEngine**