Tag Info

New answers tagged

2

From man curl -s, --silent Silent or quiet mode. Don't show progress meter or error messages. Makes Curl mute. It will still output the data you ask for, potentially even to the terminal/stdout unless you redirect it. So if you don't want any output use: curl -s 'http://example.com' > /dev/null


2

The curl command is executed but its output is not assigned to num_redirect. This means that the output of curl is shown, i.e. "3" (without a newline). However, a newline is inserted when echo $num_redirect is run, as the variable is empty. This gives you the impression that the variable num_redirect has the value of "3". You should either use backticks or ...


1

Download the latest version of the libcurl rpm from rpmfind.net or your preferred mirror and run: rpm -e --nodeps libcurl rpm -ivh libcurl PS: I think that your problem is same as Bugzilla 960765


1

Do you understand simple syntax? while IFS=',' read -r UUID protocol username passwd ip_address do curl_call="${protocol}://${username}:${passwd}@${ip_address}/report" echo $curl_call done < test_data.txt


0

It sounds like your system is missing a Python cryptographic library file that is required by yum. You should get better diagnostic information by launching the python command interpreter and entering import yum. You can then edit your question to include this information.


0

The data is sent with the content type application/x-www-form-urlencoded. In principle, %40 should be decoded to @, so the following command should send equivalent data: curl http://localhost/ --data %40hello However this may or may not work depending on whether the server-side application actually performs URL decoding. If it expects unencoded data, ...


2

Without trying to find out more about the internals of curl, I would suggest just piping into it: printf @hello | curl http://localhost/ --data @- As @ulrich-schwarz suggested in a comment, you could also use --data @<(echo @hello) if it's more convenient (not all shells support this syntax). Looking at the source code for curl-7.41.0, I don't see any ...


0

Starting with Mavericks, Apple switched the TLS/SSL engine from OpenSSL to their own Secure Transport engine in Apple distributed curl binary which breaks client certificate usage. Use the curl binary from homebrew.


0

Some sites disable support for SSL 3.0 (possible because of many exploits/vulnerabilities), so it's possible to force specific SSL version by either -2/--sslv2 or -3/--sslv3. Also -L is worth a try if requested page has moved to a different location. In my case it was a curl bug, so curl needed to be upgraded to the latest version (>7.40) and it worked ...



Top 50 recent answers are included