assertTrue(restriction.isUpperBoundInclusive(), CHECK_UPPER_BOUND_INCLUSIVE);

        range1 = VersionRange.createFromVersionSpec("[1.0,1.2],[1.3,1.5]");
        range2 = VersionRange.createFromVersionSpec("[1.1,1.4],[1.5,]");
        mergedRange = range1.restrict(range2);
        assertNull(mergedRange.getRecommendedVersion(), CHECK_VERSION_RECOMMENDATION);
        restrictions = mergedRange.getRestrictions();

                    <mxGeometry relative="1" as="geometry">
                        <mxPoint x="415" y="680" as="sourcePoint"/>
                        <mxPoint x="110" y="275" as="targetPoint"/>
                        <Array as="points">
                            <mxPoint x="245" y="710"/>
                        </Array>

                    <mxGeometry relative="1" as="geometry">
                        <mxPoint x="415" y="680" as="sourcePoint"/>
                        <mxPoint x="110" y="275" as="targetPoint"/>
                        <Array as="points">
                            <mxPoint x="245" y="710"/>
                        </Array>

                    <mxGeometry relative="1" as="geometry">
                        <mxPoint x="415" y="680" as="sourcePoint"/>
                        <mxPoint x="110" y="275" as="targetPoint"/>
                        <Array as="points">
                            <mxPoint x="245" y="710"/>
                        </Array>

		},
	}, {
		maker: makeSparse{makeReg{"abcdefghEXTRA", 13}, sparseDatas{{1, 3}, {6, 5}}, 15},
		tests: []testFnc{
			testRemaining{15, 13},
			testWriteTo{fileOps{int64(1), "abc", int64(2), "defgh", int64(4)}, 15, errUnrefData},
			testRead{100, "", errUnrefData},
			testRemaining{0, 5},
		},
	}}

	for i, v := range vectors {
		var fr fileReader
		switch maker := v.maker.(type) {
		case makeReg:

headers are now properly handled as per the HTTP spec.  As a consequence, if
you had a client that was sending an invalid Content-Type or Accept header to
the API, in 1.2 you will either receive a 415 or 406 error.
The only client
this is known to affect is curl when you use -d with JSON but don't set a
content type, helpfully sends "application/x-www-urlencoded", which is not
correct.