You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
I feel regex might be overkill for initial use case, although zk-regex is an already audited library that we should first look towards.
The text was updated successfully, but these errors were encountered: