Jadpo is experimental and not ready for production. These docs follow the compiler's main branch as of 30 Oct 2026. What's built · Install 0.1.0
jadpo
Reference: HTTP

HTTP · rule

route.header_name_invalid

Header name is not a valid HTTP header name.

Area 7, HTTP; not declinable; the next step is usually the agent's.

A field read from a header names it as HTTP writes it:

example
type Memo = Text {    max_length: 200}type MemoId = Uuid {}type AddMemo = Input {    text: Memo}type MemoView = Output {    text: Memo}action add_memo(input: AddMemo) -> MemoView {    return MemoView {        text: input.text    }}type TaggedMemo = Input {    text: Memo    tag: Memo {        header: "Request Tag"        optional: true    }}action add_tagged_memo(input: TaggedMemo) -> MemoView {    return MemoView {        text: input.text    }}policy {    actions: {        add_tagged_memo: [Access.public]    }}routes Memos {    prefix: /memos    POST / {        authentication: RouteAuthentication.none        input: TaggedMemo        output: MemoView        run: add_tagged_memo(input)    }}
text
error: `Request Tag` isn't a header name --> main.jadpo:24:17   |24 |         header: "Request Tag"   |                 ^^^^^^^^^^^^^ not a header name  reason: A header name is letters, digits and `-` (HTTP allows a few more symbols), with no spaces: `X-Request-Tag`.  next: Write the header's name without spaces (agent)  rule: route.header_name_invalid  help: https://jadpo.dev/docs/errors/route.header_name_invalidcheck failed: 1 error, 1 file

Markdown for agents: /docs/errors/route.header_name_invalid.md.Built from Jadpo main at a707efb.