I am using Authorize.net in my application(its in OSCOMMERCE) , When the user making payment its returning empty response. I debugged and find that it returning this error:
Protocol https not supported or disabled in libcurl
I am sending a prober url starts with https there is no space in that
https://secure.authorize.net/gateway/transact.dll
My application in shared hosting server. My doubt is this is server side problem or Programming problem ?
hakre
189k51 gold badges426 silver badges824 bronze badges
asked Mar 7, 2012 at 4:24
I had this problem and it was because of space in url:
' https://www.google.com/recaptcha/api/siteverify'
as you see there is a space before https
answered Dec 26, 2017 at 11:52
parastooparastoo
2,0351 gold badge18 silver badges35 bronze badges
1
For those that have https support but still get an error similar to below
[curl] 1: Protocol %20https not supported or disabled in libcurl [url] %20https://www.example.com/%20
Ensure that the URL is valid
- Try on a basic URL such as https://www.example.com
- Check your URLs and make sure no spaces at start/end of URL (as shown above as %20)
- Check for characters in your URL likely to break the curl request
AnNaMaLaI
4,0369 gold badges52 silver badges92 bronze badges
answered Jan 29, 2015 at 17:11
CarltonCarlton
5,4034 gold badges52 silver badges71 bronze badges
2
Create a script called info.php and in it put <?php phpinfo(); ?>
. Save it somewhere on your site so you can access it from a browser.
Find the curl section and check what Protocols are supported. If https
is not listed, then cURL was not built with SSL support and you cannot use https.
You can also look in the very first section for Registered PHP Streams
and see if https
is listed. If so, then you can fallback to use PHP’s socket functions or functions such as file_get_contents()
or fopen
with a context.
Since you mention you are on a shared host, request that your host recompile PHP so that both PHP and curl are built with OpenSSL support so you can use encryption, otherwise you will need to find another solution.
answered Mar 7, 2012 at 4:34
drew010drew010
68.1k11 gold badges134 silver badges160 bronze badges
4
Lately I had to use the CURL command line tool to debug a Web Service Endpoint connection.
But every time I ran this I got this Error message ?
Note: Unnecessary use of -X or –request, GET is already inferred.
* Protocol “‘https” not supported or disabled in libcurl
* Closing connection -1
curl: (1) Protocol “‘https” not supported or disabled in libcurl
Actually this Error is putting you on the wrong leg !
It’s nothing to do with unsupported protocol but rather with wrong command line formatting.
In the windows version of CURL, you need to enclose the command with double quotes, instead of single quotes.
This will not work !
curl -v -u your.name@mysite.com:password -X GET 'https://webservices.com/api/?query="priority:3"'
SOLUTION :
So you need to start and end with double quotes !
But this will give an other issue where the query string needs double quotes as well ?
This is how it should look :
curl -v -u your.name@mysite.com:password -X GET "https://webservices.com/api/?query=%22priority:3%22"
Where you replace the double quotes in the Query string with the URL encode version being %22
Enjoy!
This entry was posted on Tuesday, August 6th, 2019 at 2:40 pm and is filed under Client, Windows. You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
I did this
I installed libcurl with the following commands:
$ git clone https://github.com/curl/curl
$ cd curl
$ ./buildconf.bat
$ mingw32-make mingw32
$ cp lib/libcurl.a /c/MinGW/lib
$ cp -r include/curl/ /c/MinGW/include
I wrote this program to test it out:
// main.cpp #include <iostream> #include <curl/curl.h> int main(void) { CURL *curl; curl_global_init(CURL_GLOBAL_ALL); curl = curl_easy_init(); curl_easy_setopt(curl, CURLOPT_VERBOSE, 1L); curl_easy_setopt(curl, CURLOPT_URL, "https://api.ecs.rocks/v0/util/removeMessageHeader"); curl_easy_perform(curl); curl_free(curl); return 0; }
I built the C++ program with the following command:
$ g++ main.cpp -o curltest -m32 -DCURL_STATICLIB -lcurl -lws2_32 -lwldap32 -lwsock32 -lwinmm
And I ran it:
I expected the following
A response of some kind from https://api.ecs.rocks/v0/util/removeMessageHeader
I got the following
* Protocol "https" not supported or disabled in libcurl
* Closing connection -1
curl/libcurl version
curl 7.71.1 (x86_64-w64-mingw32) libcurl/7.71.1 OpenSSL/1.1.1g (Schannel) zlib/1.2.11 brotli/1.0.7 libidn2/2.3.0 libssh2/1.9.0 nghttp2/1.41.0
Release-Date: 2020-07-01
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp scp sftp smtp smtps telnet tftp
Features: AsynchDNS brotli HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz Metalink MultiSSL NTLM SPNEGO SSL SSPI TLS-SRP
That’s the version of curl
I have, but my version of libcurl
should be the most recent version because I built from source.
operating system
MINGW64_NT-10.0-18363 ECSS-L01 3.1.6-340.x86_64 2020-07-09 14:33 UTC x86_64 Msys
Содержание
- curl: (1) протокол https не поддерживается или отключен в libcurl
- cygwin git «Protocol «https» not supported or disabled in libcurl»
- 2 Answers 2
- Protocol https not supported or disabled in libcurl using Git
- 10 Answers 10
- Как включить поддержку https в libcurl?
- 3 ответов
- curl : (1) Protocol https not supported or disabled in libcurl
- 12 Answers 12
curl: (1) протокол https не поддерживается или отключен в libcurl
Как это можно решить?
Получил ответ ЗДЕСЬ для окон, там написано, что:
Woops, сначала попробуйте и уже ошибка:
Я столкнулся с этой проблемой и оказалось, что до места, https которое вызывало проблему, было место. » https://» против «https://»
Похоже, что ответов уже так много, но проблема, с которой я столкнулся, заключалась в двойных кавычках. Есть разница между:
Изменение 1-й двойной кавычки на вторую сработало для меня, ниже приведен пример curl:
Я столкнулся с той же проблемой при попытке установить rvm для ruby. нашел решение: после распаковки curl (tar) в папку загрузок root.
Перейти в папку с исходным кодом curl
перезагрузите консоль и все готово!
Это специально упоминается в разделе часто задаваемых вопросов libcurl » Протокол xxx не поддерживается или отключен в libcurl «.
Для вашего удовольствия я добавлю здесь объяснение:
При передаче URL-адреса для использования curl, он может ответить, что определенный протокол не поддерживается или отключен. Конкретный способ формулировки этого сообщения об ошибке заключается в том, что curl не проводит внутреннего разграничения того, не поддерживается ли конкретный протокол (т. Е. Никогда не добавлялся какой-либо код, который знает, как произносить этот протокол), или он был явно отключен. curl может быть создан для поддержки только определенного набора протоколов, а остальные будут отключены или не поддерживаются.
В моем случае протокол HTTPS не был поддержан libcurl. Чтобы выяснить, какие протоколы поддерживаются, а какие нет, я проверил версию curl с помощью команды:
Он предоставил следующую информацию: curl 7.50.3 (x86_64-apple-darwin15.6.0) libcurl/7.50.3 SecureTransport zlib/1.2.5 Протоколы: файл dict ftp ftps gopher http imap imaps ldap ldaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp Особенности: IPv6 Largefile NTLM NTLM_WB SSL libz UnixSockets
где протокол https не поддерживается.
Затем я переустановил curl и установил его, используя следующие команды (после распаковки):
И после нескольких минут работы проблемы решены!
Затем я перезапустил команду curl version, которая показала:
curl 7.50.3 (x86_64-apple-darwin15.6.0) libcurl/7.50.3 SecureTransport zlib/1.2.5 Протоколы: файл dict ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp Особенности: Крупный файл IPv6 NTLM NTLM_WB SSL libz UnixSockets
Источник
cygwin git «Protocol «https» not supported or disabled in libcurl»
curl 7.39.0 (x86_64-unknown-cygwin) libcurl/7.39.0 OpenSSL/1.0.1k zlib/1.2.8 libidn/1.29 libssh2/1.4.2 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp scp sftp smtp smtps telnet tftp Features: Debug IDN IPv6 Largefile GSS-API SPNEGO NTLM NTLM_WB SSL libz TLS-SRP Metalink
I think this means https is supported by curl. Can anyone help me? Thanks in advance.
2 Answers 2
As a workaround to using HTTPS, you can switch to using SSH as your protocol for git. When I clone repositories, I usually use SSH, since it’s a little more flexible and I have to deal with proxies sometimes. Changing your protocol can be accomplished by switching the URLs of your GitHub remote. If you list the remotes you currently have, you’ll see something like (assuming you’re in your project directory):
You can switch from HTTPS to SSH protocol with the git remote set-url command, as documented here. You’ll pass it the remote name, which’ll be origin by default:
and you should be good to go.
I think this means https is supported by curl.
To keep GitHub as secure as possible for every user, we will remove RC4 support in our SSL configuration on github.com and in the GitHub API on January 5th 2015.
Try and upgrade curl: the current package (July 2015) is curl-7.43.0-1.
Note: instead of Cygwin, you can use the latest Git for Windows: simply uncompress PortableGit-2.4.5.1-4th-release-candidate-64-bit.7z.exe anywhere you want and launch a bash session (like a lightweight cygwin, with 200+ Linux commands).
That includes a curl compatible with GitHub:
Источник
Protocol https not supported or disabled in libcurl using Git
I have a few github repos and they have been working fine for the last few months.
However, a few days ago I started getting a strange error when trying to push
and pull:
I have not changed anything that I am aware of, so not sure
where the error is coming from. Thanks in advance.
10 Answers 10
This error appears if you install Pure Data, may be it’s your case.Here is described conflict between Pure Data and git. Pure Data installer put it’s own libcurl-4.dll in system32 folder.
Even if you didn’t install Pure Data there is probably another libcurl-4.dll somwhere in your library path which is loaded before libcurl-4.dll from installed git location.
The first answer is correct though in my case it was not PureData and I even couldn’t found what program was conflicting. So I searched the libcurl.dll in C drive and cut it from SysWOW64 folder and pasted on desktop. Looked into its details and it was by some «shenzhen moyea software» which on google led me to youtube converted once installed by my lil bro. Anyways removing the file made the git working again.
Maybe you have different libcurl.dll versions installed and one of them is overwriting the github one(that does support https).
I don’t know what’s your OS, but in windows you have to change the PATH settings, so it will point to the right libcurl.dll (do a libcurl search on c: to know where is the github one).
In my case it was the Pure Data install that messed up with libcurl.dll from github.
I had the same behaviour. I don’t know why but I solved it by changing the Repo orign to ssh/git protocol
If someone unable to solve the libcurl issue, you can apply this fix
Источник
Как включить поддержку https в libcurl?
если я не упускаю что-то, это выглядит хорошо для меня. Заметьте, что https в списке протоколов.
$ which curl дает подозрительный ответ:
Хммммм. может быть!—12—> использует curl (в /usr/bin/curl ). Давайте см.:
BTW: я получаю ту же ошибку, если пытаюсь использовать https URL с любым git РЕПО на моей машине.
обновление: я смог определить путь к libcurl.4.dylib это git (и brew ) используются, следуя методу deltheil ниже. Путь:
поэтому я попробовал это:
но он все еще бросает мне эту ошибку:
3 ответов
как я могу определить путь к завитку, который использует brew?
выполнить which git чтобы определить, какая версия используется (моя установлен под /usr/local ).
затем сканируйте общие библиотеки, используемые следующим образом:
С libcurl использует версию git exec не имеет поддержки HTTPS, это расскажет вам, что это за версия и где она установлена.
это сработало для меня:
переустановите curl и установите его с помощью следующих команд (после распаковки):
полезный сайт для ссылки, когда вы сталкиваетесь с проблемами curl:https://curl.haxx.se/docs/install.html
У меня была эта проблема на OSX. Проблема была в дублировании завитка и завитка.файлы конфигурации внутри usr/local/bin, которые конфликтовали с теми же двумя файлами в usr / bin. Я удалил первый набор в местные/bin, и терминал работал после этого.
Источник
curl : (1) Protocol https not supported or disabled in libcurl
How can this be resolved?
12 Answers 12
Got the answer HERE for windows, it says there that:
Woops, first try and already an error:
The reason for this error is kind of stupid, Windows doesn’t like it when you are using single quotes for commands. So the correct command is:
I ran into this problem and turned out that there was a space before the https which was causing the problem. » https://» vs «https://»
Looks like there are so many Answers already but the issue I faced was with double quotes. There is a difference in between:
Changing the 1 st double quote to the second worked for me, below is the sample curl:
I encountered the same problem while trying to install rvm for ruby. found the solution: after extracting curl (tar) in downloads folder of root.
In my case, HTTPS protocol was not supported by libcurl at the first place. To find out which protocols are supported and which are not, I checked the curl version using command:
It provided information as follows: curl 7.50.3 (x86_64-apple-darwin15.6.0) libcurl/7.50.3 SecureTransport zlib/1.2.5 Protocols: dict file ftp ftps gopher http imap imaps ldap ldaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp Features: IPv6 Largefile NTLM NTLM_WB SSL libz UnixSockets
where https protocol happens to be not supported.
Then I re-installed curl and installed it using the following commands(after unpacked):
And after several minutes of work, Problems resolved!
Then I re-run the curl version command, it showed:
curl 7.50.3 (x86_64-apple-darwin15.6.0) libcurl/7.50.3 SecureTransport zlib/1.2.5 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp Features: IPv6 Largefile NTLM NTLM_WB SSL libz UnixSockets
Источник
Asked
6 years, 5 months ago
Viewed
108k times
When I try curl http://google.com
it works however when I do it with https, it gives this error:
curl: (1) Protocol "https" not supported or disabled in libcurl
I’ve searched for various answers but none explains how to fix it?
andrew.46♦
36k22 gold badges146 silver badges225 bronze badges
asked Sep 5, 2016 at 10:45
6
Please install curl
with SSL
Download:
- curl Releases and Downloads
Installing with SSL:
-
Unzip -> open terminal inside the directory PATH and type:
./configure --with-ssl make sudo make install
You can also specify the path to SSL installation, see ./configure --help
for details
answered Sep 5, 2016 at 14:45
BennyBenny
4,6722 gold badges17 silver badges33 bronze badges
4
A quick google found this curl FAQ on troubleshooting this problem.
But I actually would suggest to delete your current manual install of curl, and just install it with sudo apt-get install curl
. The default Ubuntu install has the right libraries for https (and many more).
answered Sep 7, 2016 at 7:04
JeroenJeroen
1816 bronze badges
1
Hi, Team.
I tested the creation of the jira project in cURL by referring to the URL below.
https://developer.atlassian.com/cloud/jira/platform/rest/v3/#api-api-3-project-post
I get the following error:
C:ideaiccurl>curl —request POST —url ‘https://domain:8080/rest/api/3/project’ —header ‘Authorization: Bearer ‘ —header ‘Accept: pplication/json’ —header ‘Content-Type: application/json’ —data ‘{«key»: «EX»,»name»: «Example»,»projectTypeKey»: «business»,»projectTemplateKey»: «com.atlassian.jira-core-project-templates:jira-core-simplified-project-management»,»description»: «Example Project description»,»leadAccountId»: «bd429c95-e27b-4423-a0bd-421cf3d69129″,»url»: «http://domain:8080″,»assigneeType»: «PROJECT_LEAD»,»avatarId»: 10200,»issueSecurityScheme»: 10001,»permissionScheme»: 10011,»notificationScheme»: 10021,»categoryId»: 10120}’curl: (1) Protocol «‘https» not supported or disabled in libcurlcurl: (6) Could not resolve host: Bearercurl: (6) Could not resolve host: ‘curl: (6) Could not resolve host: pplicationcurl: (6) Could not resolve host: applicationcurl: (6) Could not resolve host: EX,namecurl: (6) Could not resolve host: Example,projectTypeKeycurl: (6) Could not resolve host: business,projectTemplateKeycurl: (6) Could not resolve host: com.atlassian.jira-core-project-templates:jira-core-simplified-project-management,descriptioncurl: (6) Could not resolve host: Example Project description,leadAccountIdcurl: (6) Could not resolve host: bd429c95-e27b-4423-a0bd-421cf3d69129,urlcurl: (6) Could not resolve host: domain:8080,assigneeTypecurl: (6) Could not resolve host: PROJECT_LEAD,avatarIdcurl: (6) Could not resolve host: 10200,issueSecuritySchemecurl: (6) Could not resolve host: 10001,permissionSchemecurl: (6) Could not resolve host: 10011,notificationSchemecurl: (6) Could not resolve host: 10021,categoryIdcurl: (3) [globbing] unmatched close brace/bracket in column 6
C:ideaiccurl>
What did wrong?
Alex
3 answers
2 accepted
Suggest an answer
Still have a question?
Get fast answers from people who know.
Was this helpful?
Thanks!
I am trying to run a curl
command and getting this error:
'http" not supported or disabled in libcurl
I looked where I have curl.exe
, found it in C:Program FilesGDAL
and deleted it.
The error persisted. This was curl.exe
in C:Anaconda3Librarybin
, so I deleted it too.
The error still persisted. There was one more curl.exe
in the $PATH
.
So error is independent of the executable. How can I fix it?
bertieb
7,23436 gold badges40 silver badges52 bronze badges
asked May 14, 2018 at 14:47
1
Ensure you are supplying curl
with double quotes ("
), not single quotes ('
)
Curl in Windows is know to not like single quotes as per (for example) this thread:
D:nrplatform_installer_win32>curl -X GET 'http://api.newrelic.com/v2/applications.json' -H "X-Api-Key:${APIKEY}" -i curl: (1) Protocol "'http" not supported or disabled in libcurl
(…)
I believe the first warning you’re seeing is due to wrapping the url in single quotes instead of double.
(from NewRelic forums, emphasis mine)
This also popped up in a QA over on StackOverflow.
answered May 14, 2018 at 14:56
bertiebbertieb
7,23436 gold badges40 silver badges52 bronze badges