Skip to content

http: universal url match #27

@lonerapier

Description

@lonerapier

Currently, http_parse_and_lock_start_line file uses exact string match to check request URL, but some authenticated URL contains user-specific parameters like:

  • /v1/users/{{user_id}}/playlists
  • /v1/me/top/tracks?limit={{limit}}

Investigate:

  • solution possible:
    • regex
    • any other??
  • whether this should be added as a separate template based on constraint count

I feel regex might be overkill for initial use case, although zk-regex is an already audited library that we should first look towards.

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature ✨New feature or core functionality

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions