Skip to content

S
spring-framework

爱吃血肠 / spring-framework

通知 1
Star 0
Fork 0
S
spring-framework

前往新版Gitcode，体验更适合开发者的 AI 搜索 >>

切换分支/标签
  1. 07 11月, 2019 2 次提交
  3. 16 9月, 2019 1 次提交
  5. 28 3月, 2019 2 次提交
  7. 26 3月, 2019 1 次提交
  9. 23 3月, 2019 1 次提交
  11. 04 2月, 2019 2 次提交
  13. 19 11月, 2018 1 次提交
    • H
      Fix typos · bfb49c72
      由 Hanope 提交于 
      See gh-2019
      bfb49c72
  15. 17 11月, 2018 1 次提交
  17. 12 11月, 2018 1 次提交
  19. 15 10月, 2018 1 次提交
  21. 03 9月, 2018 1 次提交
  23. 15 8月, 2018 2 次提交
    • B
      Revert "Infer HTTP 404 from empty Optional/Publisher types" · f2506ca7
      由 Brian Clozel 提交于 
      This reverts commit 7e917335.
      f2506ca7
    • B
      Infer HTTP 404 from empty Optional/Publisher types · 7e917335
      由 Brian Clozel 提交于 
      This commit handles "empty" cases for `ResponseEntity` controller
handler return types when wrapped with a `java.util.Optional` in Spring
MVC or a single `Publisher` like `Mono`.

Given the following example for Spring MVC:

```
@GetMapping("/user")
public Optional<ResponseEntity<User>> fetchUser() {
	Optional<User> user = //...
	return user.map(ResponseEntity::ok);
}
```

If the resulting `Optional` is empty, Spring MVC will infer a
`ResponseEntity` with an empty body and a 404 HTTP response status.

The same reasoning is applied to Spring WebFlux with Publisher types:

```
@GetMapping("/user")
public Mono<ResponseEntity<User>> fetchUser() {
	Mono<User> user = //...
	return user.map(ResponseEntity::ok);
}
```

This feature is only valid for `HttpEntity` return types and does not
apply to `@ResponseBody` controller handlers.

Issue: SPR-13281
      7e917335
  25. 12 8月, 2018 1 次提交
  27. 09 8月, 2018 2 次提交
  29. 24 7月, 2018 1 次提交
  31. 20 7月, 2018 1 次提交
  33. 18 7月, 2018 1 次提交
  35. 17 7月, 2018 3 次提交
  37. 11 7月, 2018 1 次提交
  39. 10 7月, 2018 1 次提交
    • B
      Refine Content-Range support for Resources · 818e4b07
      由 Brian Clozel 提交于 
      This commit restricts the support of `"Content-Range"` when returning
`Resource` instances from Controllers - now only "HTTP 200 OK" responses
will be considered, as Controllers might want to handle content range
themselves.

Issue: SPR-16921
      818e4b07
  41. 28 6月, 2018 2 次提交
    • P
      Use tabs rather than spaces in tests · a89e716c
      由 Phillip Webb 提交于 
      Update tests to ensure that tabs are used instead of spaces. Also
consistently apply a new line at the end of each file.

Issue: SPR-16968
      a89e716c
    • P
      Polish test code · 1c25cec4
      由 Phillip Webb 提交于 
      Polish a few issue identified when adding checkstyle to the
build. Although checkstyle is not enforcing rules on tests,
these are a few minor changes that are still worth making.

Issue: SPR-16968
      1c25cec4
  43. 15 6月, 2018 1 次提交
  45. 08 6月, 2018 2 次提交
  47. 30 5月, 2018 1 次提交
  49. 15 5月, 2018 1 次提交
  51. 14 5月, 2018 1 次提交
  53. 11 5月, 2018 1 次提交
    • R
      Remove individual detection of forwarded headers · 4da43de7
      由 Rossen Stoyanchev 提交于 
      This commit removes all places where forwarded headers are checked
implicitly, on an ad-hoc basis.

ForwardedHeaderFilter is expected to be used instead providing
centralized control over using or discarding such headers.

Issue: SPR-16668
      4da43de7
  55. 05 5月, 2018 2 次提交
  57. 24 4月, 2018 1 次提交
    • B
      Disable HTTP Range support for InputStreamResource · e9a8a506
      由 Brian Clozel 提交于 
      Prior to this commit, the `AbstractMessageConverterMethodProcessor`
would fail to convert `InputStreamResource` to `ResourceRegion` as
expected, since the content length cannot be read without consuming the
stream. This is enforced by the `HttpRange` class.

Now the method processor would still try to output HTTP range response
headers to provide range support information. This step is using the
resource content length and reads the input stream, leading to
exceptions such as "IllegalStateException: InputStream has already been
read".

This commit improves the return type detection and excludes early
`InputStreamResource` return types. With those types, HTTP range support
is now completely disabled.

Issue: SPR-16754
      e9a8a506
  59. 12 4月, 2018 1 次提交