Loading...

XML

Word

Printable

Note that this upgrade introduced two behavioral changes that were deemed to be bugs.

~~RESTEASY-3205~~ - When the RoleBasedSecurityFilter is used, the response for errors was of type text/html even though the response itself was not valid HTML and should be text/plain.
~~RESTEASY-3443~~ - When ~~RESTEASY-3380~~ was resolved, the new ExceptionMapper returned a 500 response when it really should have been a 400. This was somewhat changed behaviors from releases prior to 6.2.7.Final. However, in some cases a 400 was also thrown. The new change always returns a 400 (Bad Request) response if a JsonProcessingException is thrown. Note this is easily worked around by adding a custom ExceptionMapper or com.fasterxml.jackson.core.JsonProcessingException
~~RESTEASY-3470~~ - It was found the Apache HTTP Client might leave connections in CLOSE-WAIT status. The fix was to evict idle and expired connections. This is hard-coded to evict these every 60 seconds.

incorporates

RESTEASY-3463 Support FormParam with EntityPart

RESTEASY-3387 Accept-Language header not parsed correctly for language subtags, variants, extension and private subtags

RESTEASY-3439 The ConfigurationBootstrap does not use the correct ConfigurationFactory

RESTEASY-3443 JsonProcessingExceptionMapper should return a 400 response rather than a 500

RESTEASY-3445 Adding headers to a list of EntityPart is not handled correctly in the writer

RESTEASY-3465 MultipartFormDataInputImpl should use a FIFO map for it's form data

RESTEASY-3468 The EntityPart.getContent(Class) and getContent(GenericType) should only be allowed to be invoked once

RESTEASY-3470 CLOSE-WAIT when using JEE REST within a Servlet Filter

RESTEASY-3473 Deprecate the publicly expose Apache HTTP Client API's and Implementations

RESTEASY-3205 RoleBasedSecurityFilter Response text/html change

(5 incorporates)