1. 27 11月, 2018 1 次提交
  2. 26 11月, 2018 2 次提交
  3. 24 11月, 2018 6 次提交
    • J
      Upgrade to Hibernate Validator 6.0.13 and EclipseLink 2.7.3 · cf31f020
      Juergen Hoeller 提交于
      Also includes Hibernate ORM 5.1.16 for integration tests.
      cf31f020
    • J
      Upgrade to Kotlin 1.2.71, OkHttp 3.12, FreeMarker 2.3.28 · 02616fba
      Juergen Hoeller 提交于
      Also includes Apache HttpClient 4.5.6 and HttpAsyncClient 4.1.4.
      02616fba
    • J
      DefaultResponseErrorHandler detects non-standard error code as well · 4a51acbe
      Juergen Hoeller 提交于
      Issue: SPR-17439
      4a51acbe
    • J
      Polishing · 3d7e373e
      Juergen Hoeller 提交于
      (cherry picked from commit 77ab88b1)
      3d7e373e
    • S
      Ensure that MethodParameter.findParameterIndex() is thread-safe · f0e69e06
      Sam Brannen 提交于
      Prior to this commit, parallel invocations of
      MethodParameter.findParameterIndex() (invoked indirectly via
      SynthesizingMethodParameter.forParameter() and
      MethodParameter.forParameter()) could intermittently lead to an
      IllegalArgumentException being thrown due to a race condition in the
      internal implementation of the JDK's
      java.lang.reflect.Executable.getParameters() method.
      
      This commit addresses this issue by introducing a fallback for-loop
      that iterates over the candidate parameters a second time using
      equality checks instead of identity checks.
      
      Issue: SPR-17534
      
      (cherry-picked from commit 81fde5ec)
      f0e69e06
    • S
      Ensure that parameter resolution in SpringExtension is thread-safe · cd67b285
      Sam Brannen 提交于
      Prior to this commit, parallel execution of @BeforeEach and @AfterEach
      methods that accepted @Autowired arguments would fail intermittently
      due to a race condition in the internal implementation of the JDK's
      java.lang.reflect.Executable.getParameters() method.
      
      This commit addresses this issue by creating instances of
      SynthesizingMethodParameter via
      SynthesizingMethodParameter.forExecutable(Executable, int) instead of
      SynthesizingMethodParameter.forParameter(Parameter), since the latter
      looks up the parameter index by iterating over the array returned by
      Executable.getParameters() (which is not thread-safe).
      
      Issue: SPR-17533
      cd67b285
  4. 23 11月, 2018 8 次提交
  5. 22 11月, 2018 1 次提交
  6. 21 11月, 2018 3 次提交
  7. 19 11月, 2018 1 次提交
    • B
      Remove Content-Length response header from errors · 5342c6e4
      Brian Clozel 提交于
      Prior to this commit, when errors happened before the response was
      committed, the `Content-Length` response header would be left as is.
      This can be problematic since the error can be handled later in the
      chain and the response body changed accordingly. For example, Spring
      Boot renders error pages in those cases. If the `Content-Length` is set,
      HTTP clients can get confused and only consider part of the error
      response body.
      
      This commit ensures that any `Content-Length` response header is removed
      in case of errors, if the response is not already committed.
      
      This is done at the `AbstractServerHttpResponse` level, since errors can
      be handled in multiple places and the response itself is the safest
      place to handle this case.
      
      As a consequence, this commit also removes `Content-Length` checks in
      `EncoderHttpMessageWriter` since we now consider that we should rely on
      the response body we're about to write rather than any previously set
      value.
      
      Issue: SPR-17502
      (Cherry-picked from 3203d398)
      5342c6e4
  8. 17 11月, 2018 1 次提交
  9. 10 11月, 2018 1 次提交
  10. 09 11月, 2018 2 次提交
  11. 08 11月, 2018 1 次提交
  12. 06 11月, 2018 8 次提交
  13. 02 11月, 2018 1 次提交
    • R
      Fix failing test · 3bb11a01
      Rossen Stoyanchev 提交于
      After the fix #658c7f for lenient parsing of dates, the error message
      raised uses an HttpHeaders-formatted date. As a result the test
      verifying the error message fails in the beginning of the month between
      1-9 because it's formatted slightly differently.
      3bb11a01
  14. 27 10月, 2018 2 次提交
  15. 26 10月, 2018 2 次提交
    • B
      Configure ResourceUrlProvider in WebFlux · 2d14bd70
      Brian Clozel 提交于
      Prior to this commit, no `ResourceUrlProvider` was configured
      in WebFlux (no bean was contributed by the WebFlux infrastructure).
      Also, several `ResourceTransformer` instances that extend the
      `ResourceTransformerSupport` base class need a `ResourceUrlProvider`
      to resolve absolute URLs when rewriting resource URLs. At this point,
      no `ResourceUrlProvider` was configured and they could only resolve
      relative URLs.
      
      This commit contributes a new `ResourceUrlProvider` to the WebFlux
      configuration; this bean can be reused by the WebFlux infrastructure and
      application code.
      
      This also automatically configure this shared `ResourceUrlProvider`
      instance on the resource chain where needed.
      
      Issue: SPR-17433
      (Cherry-picked from fc957e95)
      2d14bd70
    • J
      Polishing · 2acfb2e0
      Juergen Hoeller 提交于
      2acfb2e0