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
Params in Multipart Form Data according to grammar of Hurl accepts key-value, with key-string in it, accepting = <(alphanum | "_" | "-" | "." | escape-char)+ >
By the way, there are cases, where key-string must contain brackets, like on the image:
I tried several ways to encode (\u005b\u005d), escape (\) characters, but no result.
So for instance, '[]' (ascii square brackets or box brackets) should be accepted by Hurl.
We might add the reasonable restriction that the key-string does not start with a '['.
So that there is no ambiguities in the parsing with the section name.
For example
[FormParams]
x[Cookies] # parsed as a form param
[Cookies] # parsed as Cookie section
[xxx] # parsing error - invalid section name
Hello,
Params in Multipart Form Data according to grammar of Hurl accepts key-value, with key-string in it, accepting
= <(alphanum | "_" | "-" | "." | escape-char)+ >
By the way, there are cases, where key-string must contain brackets, like on the image:
I tried several ways to encode (\u005b\u005d), escape (\) characters, but no result.
So for instance, '[]' (ascii square brackets or box brackets) should be accepted by Hurl.
The following Hurl file should be valid:
Actually, Hurl raises an error:
The text was updated successfully, but these errors were encountered: