- 26 9月, 2019 1 次提交
-
-
由 Rossen Stoyanchev 提交于
Bypass server cookie and write Set-Cookie header directly for Reactor Netty, and Servlet API which do not provide options. For Undertow use the sameSite attribute. Closes gh-23693
-
- 25 9月, 2019 7 次提交
-
-
由 Juergen Hoeller 提交于
Includes Netty 4.1.39 (aligned with Reactor) and Checkstyle 8.24.
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Closes gh-23641
-
由 Juergen Hoeller 提交于
Closes gh-23635
-
由 Juergen Hoeller 提交于
Also restores immediate MethodOverrides instance in AbstractBeanDefinition, avoiding potential lazy-init race condition. Closes gh-23448
-
由 Juergen Hoeller 提交于
Closes gh-23593
-
由 Stephane Nicoll 提交于
Closes gh-23694
-
- 24 9月, 2019 4 次提交
-
-
由 Rossen Stoyanchev 提交于
Closes gh-23630
-
由 Rossen Stoyanchev 提交于
Closes gh-23534
-
由 Rossen Stoyanchev 提交于
Closes gh-23313
-
由 Rossen Stoyanchev 提交于
If an error looks like a "disconnected client" but the response is not yet committed then it can't be an I/O error from writing to the server response. It is most likely as a result of a remote call as part of request handling. Not setting the response to 500 in this case results in a 200 response status despite the error. Even if it was an I/O error from the server response, setting the status won't impact a failed response. Closes gh-23319
-
- 19 9月, 2019 1 次提交
-
-
由 Sam Brannen 提交于
While resolving the regression raised in gh-23571, it came to our attention that not all of our ClassFilter and MethodMatcher implementations were properly cacheable with CGLIB generated proxies due to missing (or improper) equals() and hashCode() implementations. Although such deficiencies may not manifest themselves as bugs in Core Spring's default arrangements, these might cause issues in custom arrangements in user applications. This commit addresses this by ensuring that ClassFilter and MethodMatcher implementations properly implement equals() and hashCode(). In addition, missing toString() implementations have been added to improve diagnostics for logging and debugging. Closes gh-23659
-
- 17 9月, 2019 2 次提交
-
-
由 Sam Brannen 提交于
Prior to this commit, concurrent invocations of DefaultListableBeanFactory.removeBeanDefinition() could result in a NullPointerException. This commit fixes this by adding an appropriate not-null check in resetBeanDefinition(). Closes gh-23542
-
由 Brian Clozel 提交于
Fixes gh-23631
-
- 16 9月, 2019 10 次提交
-
-
由 Stephane Nicoll 提交于
This commit makes sure that DefaultResourceLoader consistently use getProtocolResolvers() to access additional protocol resolvers. This allows subclasses to define how the list is provided. Closes gh-23564
-
由 Sam Brannen 提交于
-
由 Phillip Webb 提交于
Update the checkstyle rule to enforce the blank line between `java` and `javax`. See gh-23539
-
由 Phillip Webb 提交于
See gh-23539 Co-authored-by: NSam Brannen <sbrannen@pivotal.io>
-
由 Sam Brannen 提交于
See gh-23093 Co-authored-by: NSebastien Deleuze <sdeleuze@pivotal.io>
-
由 Juergen Hoeller 提交于
Closes gh-22926
-
由 Juergen Hoeller 提交于
See gh-22821
-
由 Sam Brannen 提交于
See gh-22821
-
由 Phillip Webb 提交于
Ensure that results returned from keySet, entrySet & values are tracked to remove case insensitive keys from the source map. Closes gh-22821
-
由 Sam Brannen 提交于
See gh-22821
-
- 13 9月, 2019 2 次提交
-
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
See: gh-23553
-
- 12 9月, 2019 4 次提交
-
-
由 Rossen Stoyanchev 提交于
On a Servlet container a completion notification may come at any time even in the UNSUBSCRIBED state, i.e. before the write Publisher has called onSubscribe. See: gh-23553
-
由 Rossen Stoyanchev 提交于
Closes: gh-23596
-
由 Rossen Stoyanchev 提交于
Closes: gh-23598
-
由 GungnirLaevatain 提交于
Prior to this commit, the copyConfigurationFrom(ConfigurableBeanFactory) method in DefaultListableBeanFactory cloned its own AutowireCandidateResolver type instead of the resolver type from the supplied ConfigurableBeanFactory. This commit fixes that by cloning the resolver type from the supplied ConfigurableBeanFactory. Closes gh-23569
-
- 11 9月, 2019 1 次提交
-
-
由 Arjen Poutsma 提交于
This commit make sure that MockClientHttpResponse does not use HttpStatus, but the raw status code. Closes gh-23599
-
- 09 9月, 2019 1 次提交
-
-
由 Sam Brannen 提交于
Prior to this commit, Spring failed to determine that an XML config file was DTD-based if the DTD declaration was followed by a comment. This commit fixes this by modifying the consumeCommentTokens(String) algorithm in XmlValidationModeDetector so that both leading and trailing comments are properly consumed without losing any XML content. Closes gh-23605
-
- 05 9月, 2019 1 次提交
-
-
由 Sam Brannen 提交于
See also: 69214429 and eec183ef
-
- 04 9月, 2019 4 次提交
-
-
由 Sam Brannen 提交于
Prior to this commit, the isSimpleProperty() and isSimpleValueType() methods in BeanUtils treated void and Void as simple types; however, doing so does not make sense in this context, since void implies the lack of a property or value. This commit addresses this by explicitly excluding void and Void in the logic in isSimpleValueType(). This commit also simplifies the implementation of ViewResolutionResultHandler.supports(HandlerResult) to take advantage of this change. Closes gh-23573
-
由 Brian Clozel 提交于
This commit reverts all artifactory configuration changes in this branch. A new build plan has been created for the master branch which is tailored for the latest Gradle changes made on that branch.
-
由 Brian Clozel 提交于
This commit adds a missing dependency from the artifactoryPublish task to the "install" task as POMs are currently missing from the published artifacts and they are generated with the "install" task here.
-
由 Brian Clozel 提交于
-
- 03 9月, 2019 1 次提交
-
-
由 Sam Brannen 提交于
Prior to this commit, ClassUtils.isPrimitiveOrWrapper() and ClassUtils.isPrimitiveWrapper() did not return true for Void.class. However, ClassUtils.isPrimitiveOrWrapper() did return true for void.class. This lacking symmetry is inconsistent and can lead to bugs in reflective code. See: https://github.com/spring-projects/spring-data-r2dbc/issues/159 This commit addresses this by adding an entry for Void.class -> void.class in the internal primitiveWrapperTypeMap in ClassUtils. Closes gh-23572
-
- 02 9月, 2019 1 次提交
-
-
由 Arjen Poutsma 提交于
This commit makes sure that reading is enabled after the current signal has been processed, not while is is being processed. The bug was only apparent while using the JettyClientHttpConnector, which requests new elements continuously, even after the end of the stream has been signalled.
-