3.4 Bugfix: prevent control characters in content-type that break the transfer encoding

[stephanr]

Currently the WFS service sends the configured mime-type as content type to the client as it got read from the configuration.

Under Weblogic this reults to a problem if the configuration is formated like the following example:

  <GMLFormat gmlVersion="GML_2">
    <MimeType>
      <![CDATA[text/xml; subtype="gml/2.1.2"]]>
    </MimeType>
    <MimeType>
      <![CDATA[text/xml; subtype=gml/2.1.2]]>
    </MimeType>
    <GetFeatureResponse>
      <DisableStreaming>true</DisableStreaming>
    </GetFeatureResponse>
  </GMLFormat>

This configuration fragment introduced additional white-space/control characters before or after the content-type so that a java/httpclient software faild to handle the transfer encoding of the result of deegree.

The effect could be fixed by removing the xml formatting, which is not a good solution as it could break any moment if someone formats the document:

  <GMLFormat gmlVersion="GML_2">
    <MimeType><![CDATA[text/xml; subtype="gml/2.1.2"]]></MimeType>
    <MimeType><![CDATA[text/xml; subtype=gml/2.1.2]]></MimeType>
    <GetFeatureResponse>
      <DisableStreaming>true</DisableStreaming>
    </GetFeatureResponse>
  </GMLFormat>