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 if a GET-request to a web page needs to be done, the full URL needs to be provided:
GET https://example.com
extract {
title: title
texts: => p
}
but it would also be useful if after the get the https:// doesn't need to be provided and can be implied.
This means that it could also be written like this:
GET example.com
extract {
title: title
texts: => p
}
Why this enhancement?
I mainly think that this should be added as it improves the usability of this language for testing and toy reasons as I sometimes just want to type in the domain as it comes to my head. And then I remember that I have to add the protocol as well.
Implementation (roughly)
I think that in this case it should try out https and then http if secure was not provided by the website. (As I'm not completely familiar with the codebase I cannot directly say on how to implement it, sorry)
The text was updated successfully, but these errors were encountered:
What is the enhancement?
Currently if a
GET
-request to a web page needs to be done, the full URL needs to be provided:but it would also be useful if after the get the
https://
doesn't need to be provided and can be implied.This means that it could also be written like this:
Why this enhancement?
I mainly think that this should be added as it improves the usability of this language for testing and toy reasons as I sometimes just want to type in the domain as it comes to my head. And then I remember that I have to add the protocol as well.
Implementation (roughly)
I think that in this case it should try out
https
and thenhttp
if secure was not provided by the website. (As I'm not completely familiar with the codebase I cannot directly say on how to implement it, sorry)The text was updated successfully, but these errors were encountered: