
Nginx Sample Config
Minimal nginx reverse-proxy config SAMPLE for syntax highlighter and linter tests.
- File
- TXT · Config
- Use case
- Config testingConversion testing
Search files, editable visual templates, and live browser targets from one registry-backed directory. Filtered query views stay crawlable for links but are deliberately noindex; the stable taxonomy pages below remain the canonical search surfaces.
Page 12 of 18; 24 results per page.

Minimal nginx reverse-proxy config SAMPLE for syntax highlighter and linter tests.

A realistic Node.js/Express stack trace — a TypeError with V8-style 'at function (file:line:col)' frames including an async frame and internal node: frames. A fixture for testing JS stack-trace parsers.

A small but complete OpenAPI 3.1 description (two paths, three schemas) in JSON — for testing API tooling, mock servers, client codegen, and docs generators.

The same OpenAPI 3.1 description in YAML — the format most API definitions ship in. Paired with the JSON twin for testing YAML↔JSON conversion and spec parsers.

Minimal OpenAPI 3.1 document with a webhooks section — for testing webhook-aware spec parsers.

Callback payload matching the Wave F webhook OpenAPI SAMPLE.

OpenAPI document with empty paths but populated components — tests partial spec loaders.

Sample POST /pets request body matching the pet-store OpenAPI spec.


Sample 404 problem response for OpenAPI error-handling tests.

Sample paginated pet list response for mock-server and contract tests.

The compatible member of a complete OpenAPI 3.1 ticket endpoint contract. Backward compatible: an optional priority response property is added and existing operations stay unchanged.

The baseline member of a complete OpenAPI 3.1 ticket endpoint contract. Reference API: string ticket IDs and required id/summary response properties.

The breaking member of a complete OpenAPI 3.1 ticket endpoint contract. Breaking relative to baseline: ticket id becomes integer and status becomes a required response property.

An OPML 2.0 subscription list with nested outline groups and three feed entries (title, xmlUrl, htmlUrl) — the format RSS readers use to import and export subscriptions, for testing OPML parsers.

The same employee table as Apache ORC — the columnar format common in the Hive/Hadoop ecosystem. For testing ORC readers and Parquet↔ORC conversion.

A fictional business contact with structured organization and postal-address fields for CRM migration tests. This member uses vCard 2.1 syntax.

A fictional business contact with structured organization and postal-address fields for CRM migration tests. This member uses vCard 3.0 syntax.

A fictional business contact with structured organization and postal-address fields for CRM migration tests. This member uses vCard 4.0 syntax.

A small employee table as Apache Parquet — the columnar format at the heart of modern data lakes and analytics. For testing Parquet readers (pandas, Spark, DuckDB) and conversion.

Amounts stored as strings in Parquet — common ingestion edge case for ETL parsers.

Parquet with dictionary-encoded string column — tests dictionary page decoding.

Parquet with repeated key values — tests join/aggregation edge cases.

Empty Parquet file with schema but no rows — edge case for readers.
We use Google Analytics and show ads via Adsterra. Non-essential cookies and ad scripts run only after you allow the matching categories. See our cookie policy.