← All tools

Set-Cookie parse

Read cookie flags without a network inspector.

Client
Name: id
Value: a
Flag 1: Path=/
Flag 2: HttpOnly
Flag 3: Secure

Nearby workflows on Toolcore

  • HTTP headers — Common request and response header fields—names, direction, and short summaries—filterable client-side. when headers, identifiers, or reference tables need a sibling check.
  • HTTP fetch test — Send GET/POST and other methods from your browser—see status and body; CORS limits apply. when headers, identifiers, or reference tables need a sibling check.
  • Accept header parse — Split Accept media types and q values. when headers, identifiers, or reference tables need a sibling check.
  • Authorization parse — Show scheme and token length (does not verify JWT). when headers, identifiers, or reference tables need a sibling check.

Common use cases

  • Set-Cookie parse for quick local checks without uploading data.
  • Copy results into tickets, docs, or classroom notes.

Common mistakes to avoid

  • Unexpected input shape

    See the intro and how-to notes for accepted formats.

FAQ

Is processing local?

Yes—this runs entirely in your browser.

Agent prefill?

Use q or qb for the main text field when supported.

More tools

Related utilities you can open in another tab—mostly client-side.