Skip to main content
The 2026 Annual Developer Survey is live— take the Survey today!

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    For future note -- backticks are for code formatting strings which are less than a single line in length. Use the {} button in the editor with a multi-line block selected, or add four spaces before each line, for longer segments. This gets you colorized syntax highlighting and generally better-looking formatting. Commented Oct 12, 2017 at 17:26
  • 1
    That said, in terms of what content a server allows -- that's the server's decision; it's not something bash or curl has any say in. If you can reproduce a problem with a publicly-available service that is explicitly documented to allow arrays, that would put us in a better place (in terms of being able to reproduce a minimal reproducible example -- roughly, the shortest possible code that someone else can run to see a problem themselves, or use to test whether their proposed answer actually fixes a problem). Commented Oct 12, 2017 at 17:34
  • 1
    (Also, "doesn't work" is not much of a description to go off of -- it doesn't tell us if you got an error from curl itself or from the remote server, f/e, and that distinction is critical. Please be sure that you provide the exact error you're asking about, going forward). Commented Oct 12, 2017 at 17:35

lang-bash