- 12 3月, 2018 2 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-16564
-
由 Juergen Hoeller 提交于
Issue: SPR-16577
-
- 11 3月, 2018 3 次提交
-
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-
由 Stephane Nicoll 提交于
-
- 10 3月, 2018 5 次提交
-
-
由 Sam Brannen 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-16547
-
由 Rossen Stoyanchev 提交于
This commit restructures the existing content to separate out Overview content into its own section, and also introduces more formal structure where reference type content can be expanded over time. Issue: SPR-16547
-
由 Rossen Stoyanchev 提交于
-
由 Sam Brannen 提交于
-
- 09 3月, 2018 15 次提交
-
-
由 Sam Brannen 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-16572
-
由 Juergen Hoeller 提交于
Issue: SPR-16571
-
由 igor-suhorukov 提交于
-
由 igor-suhorukov 提交于
-
由 igor-suhorukov 提交于
-
由 igor-suhorukov 提交于
-
由 igor-suhorukov 提交于
-
由 igor-suhorukov 提交于
-
由 igor-suhorukov 提交于
-
由 Brian Clozel 提交于
Prior to this commit, the `HttpEntityMethodProcessor` would check HTTP conditions on non-safe requests (i.e. not GET/HEAD). This would prevent Controllers from returning `ResponseEntity` containing response headers with updated values of `"Last-Modified"` or `ETag` once the resource has been updated. This commit avoids those checks for non GET/HEAD requests - this code can still be leveraged from Controllers themselves using `ServletWebRequest::checkNotModified` methods. Issue: SPR-15780
-
由 Juergen Hoeller 提交于
Issue: SPR-16570
-
由 Juergen Hoeller 提交于
-
由 igor-suhorukov 提交于
-
- 08 3月, 2018 8 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-16568
-
由 Rossen Stoyanchev 提交于
Issue: SPR-16494
-
由 Rossen Stoyanchev 提交于
After send error, ignore calls to complete or completeWithError by the application in the same thread (e.g. try-catch block), to avoid a competing with an error callback from servlet container during which the same action is taken. Issue: SPR-16548
-
由 Rossen Stoyanchev 提交于
Issue: SPR-16548
-
由 Sam Brannen 提交于
-
由 Violeta Georgieva 提交于
When checking whether there is still request body the first method that should be checked is ServletInputStream.isReady() and then ServletInputStream.isFinished(). ServletInputStream.isReady() is the active method whereas the ServletInputStream.isFinished() is not. It is important to call ServletInputStream.isReady() because if it returns false it will schedule a dispatch and if the request body is already read it will send onAllDataRead event. Issue: SPR-16521
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-16107 (cherry picked from commit b70d400c)
-
- 07 3月, 2018 7 次提交
-
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-
由 Juergen Hoeller 提交于
-
由 Patrick0308 提交于
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-