Skip to content

support any http options #1

@microcai

Description

@microcai

http options is implemented as number of classes. Is there any reason not to use a k/v based container ?
If I want to add more options, I HAVE to change the source code. That makes urdl less adaptable to regular uses.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions