Skip to content

Verify vendor-specific HTTP status codes against current primary documentation #9

Description

@MrAlfak

Goal

Strengthen the vendor dataset by re-checking entries against current first-party documentation and improving provenance where possible.

Suggested providers

Work in small batches: Cloudflare, AWS Application Load Balancer, Nginx, Microsoft IIS, Laravel, Shopify, Pantheon, or other providers already present in data/vendors.json.

What to verify

  • status number and phrase
  • provider name
  • current/legacy lifecycle
  • description
  • official documentation URL
  • whether an entry should remain historical/community-sourced

Rules

  • Prefer vendor-owned documentation.
  • Do not collapse the same numeric code across providers.
  • Keep provider-prefixed IDs stable when possible.
  • If an official source cannot be found, document that clearly rather than overstating confidence.

Acceptance criteria

  • At least one provider batch is re-verified.
  • Source metadata is improved where possible.
  • python tools/build_dataset.py and python tools/validate.py pass.
  • Tests pass and generated codes.json is updated through the normal workflow.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationhelp wantedExtra attention is needed

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions