|
In the class org.geotools.data.ows.Response there is an explicit check for content-type not being null, and if it is an exception is thrown.
This is not according to the HTTP 1.1 spec, as the Content-Type may have been omitted for a response that does not contain a body (for example when the Transfer-Encoding header is "chunked", which is acceptable always.).
We have geotools throwing an exception whenever Content-Type is not set.
(I did not look at all versions, but the ones I checked, had this code).
I included a patch to remove the check.
|
