Skip to content

Dedicated functions for accessing common response headers? #5

@damellis

Description

@damellis

Are there common response headers other than the status code that we might want to have the library parse, store, and provide functions to access? For example, the content type or content size; or redirection information;

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