I suggest you ...

Allow repeated HTTP Headers defined in the Response

Apiary only supports one occurrence of each Response Header. If multiple headers are included in the API Blueprint, only the last one is represented in the documentation.

This is problematic when documenting that an API Response sets multiple cookies.

Per RFC 6265: " Origin servers SHOULD NOT fold multiple Set-Cookie header fields into a single header field. The usual mechanism for folding HTTP headers fields (i.e., as defined in [RFC2616]) might change the semantics of the Set-Cookie header field because the %x2C (",") character is used by Set-Cookie in a way that conflicts with such folding."

Suggestion: Modify the behavior to support multiple occurrences of headers, or at least of the "Set-Cookie" header.

12 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Matt MillerMatt Miller shared this idea  ·   ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base