- 09 5月, 2017 3 次提交
-
-
由 Rossen Stoyanchev 提交于
WebHttpHandlerBuilder is low level not expected to appear frequently but they might be repeated more in tests (e.g. of WebFilter's). Issuse: SPR-15499
-
由 Rossen Stoyanchev 提交于
Issue: SPR-15520
-
由 Rossen Stoyanchev 提交于
Issue: SPR-15517
-
- 08 5月, 2017 5 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Fix javadoc of AbstractHandlerMapping#setPathMatcher
-
由 Kazuki Shimizu 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-15525
-
- 06 5月, 2017 8 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-15524
-
由 Juergen Hoeller 提交于
Also removes JDK 9 build support for the time being since Gradle 3.5 still doesn't run on JDK 9.
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-15516
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
HttpMessageConverter's are client and server and arguably shouldn't contain a server-side concept such a response status. The status field is recent, it was added to differentiate 400 vs 500 errors with Jackson 2.9+ but there is no need for it since the same distinction is reflected in raising an HttpMessageNotReadableException vs a general HttpMessageConversionException. Issue: SPR-15516
-
由 Rossen Stoyanchev 提交于
Starting with removing a package cycle on the use of ResponseStatusException in the codec package, this commit generally refines codec exception handling. The new [Encoding|Decoding]Exception mirror the existing HttpMessageNot[Readable|Writable]Exception and are used similarly especially to differentiate betwen 400 and 500 errors when parsing server request body content. The commit also aligns some of the exception handling of JSON and XML on the WebFlux side with that on the Spring MVC side. Issue: SPR-15516
-
- 05 5月, 2017 11 次提交
-
-
由 Rossen Stoyanchev 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-15497
-
由 Rossen Stoyanchev 提交于
Issue: SPR-15474
-
由 Rossen Stoyanchev 提交于
-
由 Juergen Hoeller 提交于
-
由 Rossen Stoyanchev 提交于
This comment extends the use of the charset property in FormHttpMessageConverter to also include multipart headers with a default of UTF-8. We now also set the charset parameter of the "Content-Type" header to indicate to the server side how to decode correctly. Issue: SPR-15205
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
The MultipartHttpMessageWriter now directly encodes part header values defaulting to UTF-8 and also specifies the charset in the Content-Type header for the entire request. This should work with something commonly used like Apache Commons FileUpload which checks request.getCharacterEncoding() and uses it for reading headers.
-
由 Rossen Stoyanchev 提交于
-
- 04 5月, 2017 12 次提交
-
-
由 Rossen Stoyanchev 提交于
-
由 Arjen Poutsma 提交于
This commit adds a `toParts` method in `BodyExtractors`, returning a BodyExtractor<Part>.
-
由 Juergen Hoeller 提交于
Issue: SPR-13779
-
由 Juergen Hoeller 提交于
-
由 Stephane Nicoll 提交于
-
由 Stephane Nicoll 提交于
* pr/1409: Simplify Netty dependency management by importing its bom
-
由 Eddú Meléndez 提交于
Closes gh-1409
-
由 Rossen Stoyanchev 提交于
Issue: SPR-14546
-
由 Rossen Stoyanchev 提交于
Issue: SPR-14546
-
由 Rossen Stoyanchev 提交于
This commit turns the Synchronoss NIO Multipart HttpMessageReader into a reader of Flux<Part> and creates a separate reader that aggregates the parts into a MultiValueMap<String, Part>. Issue: SPR-14546
-
由 Juergen Hoeller 提交于
Issue: SPR-15485
-
由 Juergen Hoeller 提交于
Issue: SPR-14512
-
- 03 5月, 2017 1 次提交
-
-
由 Arjen Poutsma 提交于
This commit properly closes the opened channels in the SynchronossPart, and also makes sure that the entire contents is copied, not just the first batch.
-