Skip to main content
Anybody got any clues as to why

curl -k -s -v -o htmlu.txt "https://my.url"

when issues in a shell script using sh /tmp/my.stdin would give

Protocol ""https" not supported or disabled in libcurl

when the exact same command cut/pasted onto the OMVS shell

works fine ?

Hank

------------------------------
hank oerlemans
Senior Technical Specialist
Self Registered
North Sydney NSW Australia
------------------------------
Anybody got any clues as to why

curl -k -s -v -o htmlu.txt "https://my.url"

when issues in a shell script using sh /tmp/my.stdin would give

Protocol ""https" not supported or disabled in libcurl

when the exact same command cut/pasted onto the OMVS shell

works fine ?

Hank

------------------------------
hank oerlemans
Senior Technical Specialist
Self Registered
North Sydney NSW Australia
------------------------------
Always the way.....light appears after I post.

I have to work out how to get the quotes around the URL interpreted properly by the shell I think. Backslash doesn't work.

------------------------------
hank oerlemans
Senior Technical Specialist
Self Registered
North Sydney NSW Australia
------------------------------
Anybody got any clues as to why

curl -k -s -v -o htmlu.txt "https://my.url"

when issues in a shell script using sh /tmp/my.stdin would give

Protocol ""https" not supported or disabled in libcurl

when the exact same command cut/pasted onto the OMVS shell

works fine ?

Hank

------------------------------
hank oerlemans
Senior Technical Specialist
Self Registered
North Sydney NSW Australia
------------------------------

Hi Hank,

This errors usually occurs when URL cannot be read properly.

It looks, the protocol name was read as ""https"  instead of "https". Could you check if you have extra double quotes in your script?

You can also try to skip the quotes around URL:

curl -k -s -v -o htmlu.txt https://example.com

It should work in mostly cases.

Thanks,

Sergey



------------------------------
Sergey Rezepin
Rocket Software
------------------------------

Hi Hank,

This errors usually occurs when URL cannot be read properly.

It looks, the protocol name was read as ""https"  instead of "https". Could you check if you have extra double quotes in your script?

You can also try to skip the quotes around URL:

curl -k -s -v -o htmlu.txt https://example.com

It should work in mostly cases.

Thanks,

Sergey



------------------------------
Sergey Rezepin
Rocket Software
------------------------------
Ah well I decided I am likely the worst shell scripter I know !

I am having much more success running my prototyping via Rexx - which I've been using for much longer and I can work with syscalls and spawn more easily.
Thx for taking an interest.

------------------------------
hank oerlemans
Senior Technical Specialist
Self Registered
North Sydney NSW Australia
------------------------------
Terms & ConditionsAccessibility statement