Skip to content

Proposal: http.parse_link_header (RFC 8288) #78

@jtdowney

Description

@jtdowney

In the spirit of the existing http.parse_content_disposition that implements RFC 2045, I'd like to propose the addition of http.parse_link_header defined in RFC 8288. These are the headers that look like:

Link: <http://example.com/TheBook/chapter2>; rel="previous";
         title="previous chapter"

This is common in HTTP APIs (Stripe, ACME, etc). It seems advantageous to me to have a single, well-tested version of this rather than having each client implement their own.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions