curl
Here are 1,229 public repositories matching this topic...
Description
Sending empty files in a multipart POST form is a proper use case due to web browsers supporting it.
I worked on a API layer using guzzle that had to work with an existing legacy codebase and trigger some actions (a proxy of some sort). There was a case where files had to be sent with empty content and would not work if you would omit them.
Example
_Currently no implem
Hi, I've found the following cheatsheet :
In the README you explain that there must be an edit button in the page and a github button to access the sheet but as you can see it doesn't appear here.
Thx ;)
I did this
While investigating a mailing list question I observed that CURLINFO_ACTIVESOCKET does not actually return the active socket until after the transfer is done. This appears to be due to legacy reasons, since it is a replacement for [CURLINFO_LASTSOCKET](https://curl.haxx
Is your feature request related to a problem? Please describe.
An external API does not always respond successfully. Server errors for example 50x or 429 Too Many Requests may occur. Manually pressing the send button while waiting for a successful response can be tedious.
Describe the solution you'd like
Be able to set the number of retries and the expected/unexpected status codes o
Documentation does not cover how to specify city names consisting of multiple words (Los Angeles, Hong Kong, etc). Should it be wttr.in/LosAngeles, or wttr.in/Los_Angeles, or wttr.in/Los+Angeles, or something else? This would be a useful thing to add to the Readme.
F1 simply prints "11~" in whatever field I have selected.
Debian GNU/Linux 9.5
I always feel bad about my first contact with developers being a bug report or complaint; so I wanted you to know how cool I think this. Thanks for your efforts!
The fsockopen.after_request and curl.after_request hooks don't receive an $info parameter when a non-blocking request is sent.
This means the hook signature differs depending on whether the request is blocking or not, and conflicts with the hook docs.
Possible solution: Pass an empty array as the $info parameter for thes
-
Updated
May 19, 2020 - PHP
Right now query in the nodejs api is just a string. we should support gql-parsed strings too, so that if they are exported elsewhere, it can be used directly.
import gql from 'graphql-tag';
export const GRAPHQL_QUERY=gql`
query {
something {
anotherthing
}
}
`;In order to connect to a websocket service inside a pod in a minikube setup, I need to address the Kubernetes remote API which then demands a client certificate (~/.minikube/client.crt and ~/.minikube/client.key). I also have the server's CA ( ~/.minikube/ca.crt).
curl allows to use these certs with the --cert, --key, and --cacert options.
Does websocat also support specifyin
-
Updated
May 15, 2020 - Shell
-
Updated
Oct 30, 2019 - JavaScript
-
Updated
Apr 25, 2020 - JavaScript
The vignette has a paragraph starting with "For many APIs, the common approach is to retry API calls that return something in the 500 range." but it doesn't mention the RETRY() function.
-
Updated
May 13, 2020 - Perl
-
Updated
May 7, 2020 - Go
-
Updated
Jan 24, 2020 - Python
README on Promise
The readme on Promise part is not proper. Actually, the project uses any-promise while not register bluebird. So people should be told to register their promise, otherwise the native promise would be used.
-
Updated
Apr 14, 2020 - PHP
-
Updated
Dec 9, 2017 - Swift
-
Updated
Mar 18, 2020 - PHP
I managed to build the library using refactored CMake, however it outputs a lot of warnings:
Scanning dependencies of target curlcpp
[ 7%] Building CXX object src/CMakeFiles/curlcpp.dir/curl_easy.cpp.obj
In file included from curlcpp/include/curl_easy.h:35,
from curlcpp\src\curl_easy.cpp:6:
curlcpp/include/curl_pair.h: In member function 'const curl_httppost* curl::cu
-
Updated
Apr 14, 2020 - PHP
-
Updated
May 4, 2020 - Python
Improve this page
Add a description, image, and links to the curl topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the curl topic, visit your repo's landing page and select "manage topics."

It's not clear from the website's documentation, or the
--helpoutput, how to do the following equivalent curl task:Post a raw JSON query to ElasticSearch:
T