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
Where value-string is a "common" token : in particular, as value-string, URL should accept Hurl unicode literals (ex: \u{7b}), or curly braces ({). Related to discussion #3243, we should accept the following Hurl file where the URL contains {and }without being URL encoded:
GET https://www.example.com/index.html?foo={bar}
HTTP 200
The text was updated successfully, but these errors were encountered:
Both seem OK! You can also do some "git blaming" on the function that checks the http/https prefix to see why we added it: I remember adding an integration test for it but don't remember what has triggered it...
There are some logic regarding redirection where we must transform the value of the url to an URL structure so I think we can't simply accept any value and pass it to libcurl.
In the Hurl grammar, URL is parsed as:
Where
value-string
is a "common" token : in particular, asvalue-string
, URL should accept Hurl unicode literals (ex:\u{7b}
), or curly braces ({
). Related to discussion #3243, we should accept the following Hurl file where the URL contains{
and}
without being URL encoded:The text was updated successfully, but these errors were encountered: