I propose to wait what webtier folks will say. We can leave those
properties for Grizzly and Glassfish, but assign "null" default values.
Alexey.
On Apr 26, 2010, at 17:26 , jfarcand wrote:
> Salut,
>
> On 10-04-26 11:22 AM, Justin Lee wrote:
>> Ha! whoops! that was done in response to a glassfish bug. We'll
>> have
>> to take this back to them then and probably roll this change back.
>> And
>> then probably remove some configuration options.
>
> This behavior was added in V2 because originally supported by the
> WebServer in super-wonderful Appserver 7 ;-) I didn't ported that
> changes and that was supposed to be deprecated in v3 (removed
> completely) :-)
>
> A+
>
> -- Jeanfrancois
>
>
>>
>> On 4/26/10 11:13 AM, Sebastien Dionne wrote:
>>> I found that in the servlet 2.4 specs.
>>>
>>> ---------- Forwarded message ----------
>>> From:<Sebastien.Dionne_at_videotron.com>
>>> Date: Apr 26, 2010 11:10 AM
>>> Subject: servlet 2.4 specs
>>> To:<survivant00_at_gmail.com>
>>>
>>>
>>> Servlet programmers are responsible for ensuring that the Content-
>>> Type
>>> header is appropriately set in the response object for the content
>>> the
>>> servlet is
>>> generating. The HTTP 1.1 specification does not require that this
>>> header be
>>> set in
>>> an HTTP response. Servlet containers must not set a default
>>> content type
>>> when the
>>> servlet programmer does not set the type.
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_atmosphere.dev.java.net
>> For additional commands, e-mail: users-help_at_atmosphere.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>