In = syntax,

• double quotes (")
• back slashes (\)
• non-ascii characters

are escaped in json.dumps:

$ http -v httpbin.org/post                                      \
    dquote='\"'                                                 \
    multi-line='line 1\nline 2'                               

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

Using curl with alt-svc support compiled in:

$ curl --alt-s

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.

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

curl --location --request POST 'http://example.com/api/test' \
--header 'Content-Type: multipart/form-data' \
--form 'file=@/C:/Users/Example/Pictures/index.png' \
--form 'name=test'

This is how you do multipart with http. This is for dio.

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
    }
  }
`;

I am not sure, whether I am too stupid for this or the documentation is insufficient, but I fail to handle .httr-oauth files properly. Thus, I am opening a documentation issue.

Background: I have a client using httr logins to send emails via gmailR (thanks for your work!). In general, it works just fine, but whenever he changes the password of his gmail account, he needs to update ``.ht

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.