Skip to content

Document use422ForNoDataStatusCode on the feature flags page #106

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ChrisJohnNOAA merged 1 commit into from
Sep 30, 2026
Merged

Document use422ForNoDataStatusCode on the feature flags page #106

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/server-admin/feature-flags.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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**
Expand Down