git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v6 1/1] http: add support selecting http version

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 9, 2018, 02:56 UTC
Message-ID
<xmqqzhuj5574.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<93fda67198441c159bfcf1dfa467ad76f3ecba76.1541660405.git.gitgitgadget@gmail.com>
"Force Charlie via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 19 quoted lines
> +#if LIBCURL_VERSION_NUM >=0x072f00
> +static int get_curl_http_version_opt(const char *version_string, long *opt)
> +{
> +	int i;
> +	static struct {
> +		const char *name;
> +		long opt_token;
> +	} choice[] = {
> +		{ "HTTP/1.1", CURL_HTTP_VERSION_1_1 },
> +		{ "HTTP/2", CURL_HTTP_VERSION_2 }
> +	};
> +
> +	for (i = 0; i < ARRAY_SIZE(choice); i++) {
> +		if (!strcmp(version_string, choice[i].name)) {
> +			*opt = choice[i].opt_token;
> +			return 0;
> +		}
> +	}
> +

I wonder if we need to give a warning here about an unknown and ignored value, by calling something like

	warning("unknown value given to http.version: '%s'", version_string);

here. We should not trigger noisy warning while reading the configuration file looking for other variables unrelated to http.version but this codepath is followed only when we know we need to find out what value the variable is set to, so it probably is a good thing to do.

Thoughts?
Previous: Junio C HamanoNext: Force.Charlie-I via GitGitGadget
Message 27 of 33 in “http: add support selecting http version”
  1. 0/1 http: add support selecting http versionForce.Charlie-I via GitGitGadget, Nov 7, 2018
  2. 1/1 http: add support selecting http versionForce Charlie via GitGitGadget, Nov 7, 2018
  3. Junio C HamanoNov 8, 2018
  4. Daniel StenbergNov 7, 2018
  5. brian m. carlsonNov 8, 2018
  6. Junio C HamanoNov 8, 2018
  7. 0/3 http: add support selecting http versionForce.Charlie-I via GitGitGadget, Nov 8, 2018
  8. 1/3 http: add support selecting http versionForce Charlie via GitGitGadget, Nov 8, 2018
  9. 2/3 support force use http 1.1Force Charlie via GitGitGadget, Nov 8, 2018
  10. 3/3 fix curl version to support CURL_HTTP_VERSION_2TLSForce Charlie via GitGitGadget, Nov 8, 2018
  11. 0/4 http: add support selecting http versionForce.Charlie-I via GitGitGadget, Nov 8, 2018
  12. 1/4 http: add support selecting http versionForce Charlie via GitGitGadget, Nov 8, 2018
  13. 2/4 support force use http 1.1Force Charlie via GitGitGadget, Nov 8, 2018
  14. 3/4 fix curl version to support CURL_HTTP_VERSION_2TLSForce Charlie via GitGitGadget, Nov 8, 2018
  15. 4/4 http: change http.version value typeForce Charlie via GitGitGadget, Nov 8, 2018
  16. 0/4 http: add support selecting http versionForce.Charlie-I via GitGitGadget, Nov 8, 2018
  17. 3/4 fix curl version to support CURL_HTTP_VERSION_2TLSForce Charlie via GitGitGadget, Nov 8, 2018
  18. 2/4 support force use http 1.1Force Charlie via GitGitGadget, Nov 8, 2018
  19. 4/4 http: change http.version value typeForce Charlie via GitGitGadget, Nov 8, 2018
  20. 1/4 http: add support selecting http versionForce Charlie via GitGitGadget, Nov 8, 2018
  21. 0/1 http: add support selecting http versionForce.Charlie-I via GitGitGadget, Nov 8, 2018
  22. 1/1 http: add support selecting http versionForce Charlie via GitGitGadget, Nov 8, 2018
  23. 0/1 http: add support selecting http versionForce.Charlie-I via GitGitGadget, Nov 8, 2018
  24. 1/1 http: add support selecting http versionForce Charlie via GitGitGadget, Nov 8, 2018
  25. Eric SunshineNov 8, 2018
  26. Junio C HamanoNov 9, 2018
  27. Junio C HamanoNov 9, 2018
  28. 0/1 http: add support selecting http versionForce.Charlie-I via GitGitGadget, Nov 8, 2018
  29. 1/1 http: add support selecting http versionForce Charlie via GitGitGadget, Nov 8, 2018
  30. Junio C HamanoNov 9, 2018
  31. 0/1 http: add support selecting http versionForce.Charlie-I via GitGitGadget, Nov 9, 2018
  32. 1/1 http: add support selecting http versionForce Charlie via GitGitGadget, Nov 9, 2018
  33. Junio C HamanoNov 8, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.