No probs, we were planning on stopping jersey request/response logging on
server side, it causes a lot of lines happening :) And same info is
available on client side anyways.
Paul Sandoz wrote:
>
>
> On Nov 13, 2009, at 1:46 PM, Ari Heino wrote:
>
>>
>>
>>
>> Paul Sandoz wrote:
>>>
>>> Hi,
>>>
>>> Can you try and disable the logging filter for the server response?
>>>
>>> I think there might be a bug in the LoggingFilter :-(
>>>
>>> Paul.
>>>
>>>
>> oh yeah, with LoggingFilter taken away:
>>
>> curl -i -u Mike:Mike -H "If-Modified-Since: Fri, 13 Nov 2009
>> 16:17:37 GMT"
>> http://131.207.211.203:8080/webservices/containers/SystemTestContainer/eventfeed
>> HTTP/1.1 304 Not Modified
>> Content-Type: application/atom+xml
>> Last-Modified: Fri, 13 Nov 2009 12:45:05 GMT
>> Server: Jetty(6.1.x)
>>
>> So response code arrived correctly.
>
> Damn :-( sorry about that.
>
> The adapting ContainerResponseWriter used for logging the response
> does not call ContainerResponseWriter.finish on the adapted
> ContainerResponseWriter instance.
>
> I have fixed things in my local copy of the source.
>
> Paul.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
>
>
--
View this message in context: http://n2.nabble.com/1-1-4-response-codes-with-Atom-feeds-tp3998025p3999302.html
Sent from the Jersey mailing list archive at Nabble.com.