Incorrect OData-Version header in Northwind service

Hi,

I’m writing to you because I found an issue in your public Northwind v4 service (which I love btw).

When I send a Post request to:
https://services.odata.org/v4/Northwind/Northwind.svc/$batch

Headers:

Accept:multipart/mixed
Content-Type:multipart/mixed; boundary=batch_id-1581942277805-14

Payload:

--batch_id-1581942277805-14
Content-Type:application/http
Content-Transfer-Encoding:binary

GET Products?$orderby=ProductName&$select=ProductID,ProductName,UnitPrice&$skip=0&$top=20 HTTP/1.1
Accept:application/json;odata.metadata=minimal;IEEE754Compatible=true
Accept-Language:en-US
Content-Type:application/json;charset=UTF-8;IEEE754Compatible=true

I get the following reponse:

--batchresponse_9f4b4742-3191-4a93-8d59-e22fb6ab2412
Content-Type: application/http
Content-Transfer-Encoding: binary

HTTP/1.1 200 OK
OData-Version: 4.0;
Content-Type: application/json;odata.metadata=minimal;odata.streaming=true;IEEE754Compatible=true;charset=utf-8
X-Content-Type-Options: nosniff
Cache-Control: no-cache

...

The bug occurs in the line OData-Version: 4.0; which afaik should NOT contain the semi-colon in the end.

Can you confirm that this is an incorrect header, e.g. not protocol-compliant?

Start by reproducing the request against the Northwind v4 $batch endpoint described in the issue and compare the response with the OData protocol requirements. Done means confirming whether the trailing semicolon is invalid and identifying a repository-owned component or test that could be changed; none is named in the issue.