Arjen Poutsma edc80ffa95 Use request contentType/encoding in ServletServetHttpRequest/Response ...

ServletServerHttpRequest now falls back on the contentType and the
the characterEncoding of the ServletRequest, if the headers of the
incoming request don't specify one. Similary ServletServerHttpResponse
sets the contentType and the characterEncoding of the ServletResponse
if not already set.

This allows using the CharacterEncodingFilter to set a character
encoding where the request doesn't specify one and have it be used
in HttpMessageConverter's.

SPR-9096

2012-02-09 12:34:27 -05:00

..

.settings

ModelAndViewContainer related refinements

2011-04-07 18:09:28 +00:00

src

Use request contentType/encoding in ServletServetHttpRequest/Response

2012-02-09 12:34:27 -05:00

.classpath

[SPR-8222] Upgraded to JUnit 4.9.

2011-08-30 13:16:12 +00:00

.project

adding eclipse project meta-data, .classpath file is based on dependencies listed in ivy.xml

2008-10-24 21:05:25 +00:00

build.xml

+ upgrade to AspectJ 1.6.8

2010-02-04 11:46:21 +00:00

ivy.xml

shortened build properties "org.junit.version" to "junit.version" and "org.testng.version" to "testng.version"; reverted SLF4J version back to 1.5.3 (for Hibernate 3.3.1 compatibility)

2011-06-09 09:58:15 +00:00

pom.xml

Add <license> section to 3.1.x Maven poms

2012-01-31 15:18:05 +01:00

template.mf

marked Apache HttpComponents dependency as optional (SPR-8788); cleanup of conversation dependencies

2011-10-20 09:55:09 +00:00

web.iml

updated IntelliJ dependency descriptors

2011-05-29 20:43:52 +00:00