>From the URL RFC (http://tools.ietf.org/html/rfc3986, relevant grammar
attached below) it seems that 'https://' in indeed a valid path component.
ZnUrl seems to remove empty segments (which '//' would be) but that is not
correct according to the RFC (empty segments appear to be valid components
of a URL path).
An empty path segment is valid, as "path-absolute" in your case consists of
multiple "'/' segment" sequences, where "segment" is allowed to be empty.
Your should open a bug report for this.
path = path-abempty ; begins with '/' or is empty
/ path-absolute ; begins with '/' but not '//'
/ path-noscheme ; begins with a non-colon segment
/ path-rootless ; begins with a segment
/ path-empty ; zero characters
path-abempty = *( '/' segment )
path-absolute = '/' [ segment-nz *( '/' segment ) ]
path-noscheme = segment-nz-nc *( '/' segment )
path-rootless = segment-nz *( '/' segment )
path-empty = 0<pchar>
segment = *pchar
segment-nz = 1*pchar
segment-nz-nc = 1*( unreserved / pct-encoded / sub-delims / '@' )
; non-zero-length segment without any colon ':'
pchar = unreserved / pct-encoded / sub-delims / ':' / '@'
unreserved = ALPHA / DIGIT / '-' / '.' / '_' / '~'
pct-encoded = '%' HEXDIG HEXDIG
sub-delims = '!' / '$' / '&' / ''' / '(' / ')'
/ '*' / '+' / ',' / ';' / '='
On 5 August 2017 at 03:16:16, milton mamani (akeval...@gmail.com) wrote:
Hi to all
I want to use the next instruction in my code
response := ZnEasy get: 'https://archive.softwareheritage.org/api/1/
The previous code works from command line or in a webbrowser, but I does
not work with ZnEasy
Because it takes the previous link as:
a ZnRequest(GET /api/1/origin/git/url/https:/github.com/hylang/hy)
Could you please tell me what can I do for this situation?