"⊗":                     "\u2297",
	"∲":        "\u2232",
	"”":           "\u201d",
	"’":                 "\u2019",
	"∷":                           "\u2237",
	"⩴":                          "\u2a74",
	"≡":                       "\u2261",
	"∯":                          "\u222f",
	"∮":                 "\u222e",

		"CircleTimes;":                     '\U00002297',
		"ClockwiseContourIntegral;":        '\U00002232',
		"CloseCurlyDoubleQuote;":           '\U0000201D',
		"CloseCurlyQuote;":                 '\U00002019',
		"Colon;":                           '\U00002237',
		"Colone;":                          '\U00002A74',
		"Congruent;":                       '\U00002261',
		"Conint;":                          '\U0000222F',

//		Whether the linker should use external linking mode
//		when using -linkmode=auto with code that uses cgo.
//		Set to 0 to disable external linking mode, 1 to enable it.
//	GIT_ALLOW_PROTOCOL
//		Defined by Git. A colon-separated list of schemes that are allowed
//		to be used with git fetch/clone. If set, any scheme not explicitly
//		mentioned will be considered insecure by 'go get'.

  }

  /**
   * Old implementations of OkHttp's response cache wrote header fields like ":status: 200 OK". This
   * broke our cached response parser because it split on the first colon. This regression test
   * exists to help us read these old bad cache entries.
   *
   * https://github.com/square/okhttp/issues/227
   */
  @Test
  fun testGoldenCacheResponse() {
    cache.close()

		{"foo\x00bar: foo\r\n", 400},                         // binary in header
		{"Foo: " + strings.Repeat("x", 1<<21) + "\r\n", 431}, // header too large
		// Spaces between the header key and colon are not allowed.
		// See RFC 7230, Section 3.2.4.
		{"Foo : bar\r\n", 400},
		{"Foo\t: bar\r\n", 400},

		// Empty header keys are invalid.
		// See RFC 7230, Section 3.2.
		{": empty key\r\n", 400},