- 24 7月, 2017 1 次提交
-
-
由 Spring Buildmaster 提交于
-
- 21 7月, 2017 3 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-15803
-
由 Rossen Stoyanchev 提交于
When the input stream is a JSON array the tokenizer skips over the start and end array tokens in order to decode into an array of top-level objects. However in this mode it also skips over nested start and end array tokens which prevents proper parsing of JSR-310 dates (represented with an array syntax) as well as any fields that are collections. Issue: SPR-15803
-
由 Rossen Stoyanchev 提交于
-
- 20 7月, 2017 17 次提交
-
-
由 Rossen Stoyanchev 提交于
The method was orginally added under SPR-14547 but the example in it was probably intended for use with Content-Disposition server response header (file dowonload) and not for a Content-Disposition header within the body of a multipart request. In a Spring application a multipart request is typically serialized by the FormHttpMessageConverter and hence the Content-Disposition is not explicitly set by the application. Issue: SPR-15205
-
由 Sebastien Deleuze 提交于
-
由 Sebastien Deleuze 提交于
-
由 Brian Clozel 提交于
This commit parses the "Host" HTTP request header as an `InetSocketAddress`, while supporting IPv6 addresses like `[::1]`. This host string contains `:` chars even though it has no port information. Issue: SPR-15799
-
由 Rossen Stoyanchev 提交于
StandardMultipartHttpServletRequest now properly decodes RFC-5987 encoded filenames (i.e. filename*) by delegating to ContentDisposition and also support RFC-2047 syntax through javax.mail MimeUtility. Issue: SPR-15205
-
由 Sebastien Deleuze 提交于
Issue: SPR-15798
-
由 Juergen Hoeller 提交于
Issue: SPR-15797
-
由 Juergen Hoeller 提交于
Issue: SPR-15673
-
由 Sebastien Deleuze 提交于
This commit updates BeanUtils class in order to add Kotlin optional parameters with default values support to the immutable data classes support introduced by SPR-15199. Issue: SPR-15673
-
由 Brian Clozel 提交于
Prior to this commit, the host+port information of the incoming request where taken from the remoteAddress, which is actually the socket address of the HTTP client (i.e. not the server). This commit resolves this information from the "Host" HTTP request header, if available, or the actual local address of the channel if no header is available. Issue: SPR-15084
-
由 Juergen Hoeller 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-15779
-
由 Juergen Hoeller 提交于
Issue: SPR-15786
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-15720 Issue: SPR-15792
-
由 Rossen Stoyanchev 提交于
Issue: SPR-15717
-
- 19 7月, 2017 14 次提交
-
-
由 Rob Winch 提交于
-
由 Rob Winch 提交于
Add an option for ForwardedHeaderFilter to only process the HttpServletRequest. This means that HttpServletResponse.sendRedirect will only work when the application is conifgured to use relative redirects using Servlet Container specific setup. Issue: SPR-15717
-
由 Rossen Stoyanchev 提交于
Issue: SPR-15782
-
由 Rossen Stoyanchev 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-15720 Issue: SPR-15792
-
由 Stephane Nicoll 提交于
-
由 Stephane Nicoll 提交于
Issue: SPR-15793
-
由 Sebastien Deleuze 提交于
This commit ensure that null-safety is consistent between getters and setters in order to be able to provide beans with properties with a common type when type safety is taken in account like with Kotlin. It also add a few missing property level @Nullable annotations. Issue: SPR-15792
-
由 Sebastien Deleuze 提交于
-
由 Sebastien Deleuze 提交于
-
由 Sebastien Deleuze 提交于
Issue: SPR-15755
-
由 Juergen Hoeller 提交于
Issue: SPR-15720
-
由 Sam Brannen 提交于
Issue: SPR-15791
-
由 Rossen Stoyanchev 提交于
Since there is no reason for an exchange to ever complete without a ClientResponse I've added a switchIfEmpty check at the WebClient level. Also, temporarily a second check closer to the problem in the ReactorClientHttpConnector suggesting a workaround and providing a reference to the Reactor Netty issue #138. Issue: SPR-15784
-
- 18 7月, 2017 5 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-15785
-
由 Rossen Stoyanchev 提交于
Issue: SPR-15773
-
由 Rossen Stoyanchev 提交于
Collapse the base interface VersionPathStrategy into its extension VersionStrategy and then turn the prefix nad fliename based implementations into abstract base classes (vs delegate strategies). It is simpler to have one VersionStrategy hierarchy vs that plus a separate VersionPathStrategy as a delegate. In practice each VersionStrategy is suited to be prefix or filename based. Also none of our code cares about the distinction between those two interfaces.
-
由 Juergen Hoeller 提交于
Issue: SPR-15787
-
由 Brian Clozel 提交于
Since `PathPattern.combine` now returns another `PathPattern` instance (it was previously returning a String instance), we can now safely remove the parser instance included in `PatternsRequestCondition`. Issue: SPR-15663
-