1. 22 3月, 2019 1 次提交
  2. 21 3月, 2019 2 次提交
  3. 20 3月, 2019 4 次提交
  4. 16 3月, 2019 4 次提交
  5. 15 3月, 2019 1 次提交
  6. 13 3月, 2019 3 次提交
  7. 08 3月, 2019 1 次提交
  8. 07 3月, 2019 1 次提交
  9. 25 2月, 2019 1 次提交
  10. 22 2月, 2019 1 次提交
    • B
      Remove response content-type before error handling · e47f7ef7
      Brian Clozel 提交于
      Prior to this commit, the negotiated content-type during the request
      mapping phase would be kept as the response content-type header; this
      information is used when rendering the error response and prevents a new
      round of content negotiation to choose the media type that fits best.
      
      This commit removes the response content type information at the
      beginning of the error handling phase.
      
      Fixes gh-22452
      e47f7ef7
  11. 12 2月, 2019 1 次提交
    • B
      Defer ExchangeFilterFunction to subscription time · d463598c
      Brian Clozel 提交于
      Prior to this commit, the `ExchangeFilterFunction` instances configured
      on a `WebClient` instance would be executed as soon as the `exchange`
      method would be called. This behavior is not consistent with the server
      side and can confuse filter developers as they'd need to manually
      `Mono.defer()` their implementations if they want to record metrics.
      
      This commit defers all `ExchangeFilterFunction` processing at
      subscription time.
      
      Fixes gh-22375
      d463598c
  12. 05 2月, 2019 1 次提交
    • B
      Avoid java.util.stream.Stream usage in hot paths · 862fa557
      Brian Clozel 提交于
      Prior to this commit, profiling sessions would show that using
      `java.util.stream.Stream` in some hot code paths creates significant
      garbage.
      
      Where streams aren't really required, this commit turns those snippets
      into imperative logic  because those are likely to be called once or
      multiple times per request.
      
      Closes gh-22341
      862fa557
  13. 25 1月, 2019 1 次提交
  14. 22 1月, 2019 1 次提交
    • B
      Wrap DecodingException in DefaultServerRequest · d6aa589c
      Brian Clozel 提交于
      Prior to this commit, Spring WebFlux function would let
      `DecodingException` thrown by codecs bubble up to the web handler level.
      Since this exception is not handled by default there, the response would
      be turned into a HTTP 500 status.
      
      In the annotation model, `ArgumentResolver` implementations wrap this
      exception with a `ServerWebInputException`, which itself extends
      `ResponseStatusException`. The latter is supported by the error handling
      infrastructure as a HTTP 400 response.
      
      This commit ensures that `DecodingException` instances are properly
      wrapped in `ServerWebInputException` at the `ServerRequest` level
      directly, thus supporting all setup modes ("standalone" and through the
      `DispatcherHandler`).
      
      Fixes #22290
      d6aa589c
  15. 09 1月, 2019 1 次提交
  16. 03 1月, 2019 1 次提交
    • R
      More accurate checks for presence of MediaType.ALL · 4b24bcb7
      Rossen Stoyanchev 提交于
      Typically a straight up equals as well as Collections#contains
      checks for MediaType.ALL is susceptible to the presence of
      media type parameters.
      
      This commits adds equalsTypeAndSubtype as well as an
      isPresentIn(Collection<MimeType>) methods to MimeType to faciliate
      with checks for MediaType.ALL.
      
      Issue: SPR-17550
      4b24bcb7
  17. 02 1月, 2019 1 次提交
  18. 18 12月, 2018 1 次提交
  19. 17 12月, 2018 1 次提交
  20. 12 12月, 2018 2 次提交
  21. 11 12月, 2018 1 次提交
  22. 07 12月, 2018 2 次提交
  23. 06 12月, 2018 1 次提交
  24. 05 12月, 2018 1 次提交
    • R
      Refine check for multiple subscribers · 7a5f8e03
      Rossen Stoyanchev 提交于
      Commit #c187cb2f introduced proactive rejection of multiple subscribers
      in ReactorClientHttpResponse, instead of hanging indefinitely as per
      https://github.com/reactor/reactor-netty/issues/503.
      
      However FluxReceive also rejects subsequent subscribers if the response
      is consumed fully, as opposed to being canceled, e.g. as with
      bodyToMono(Void.class). In that case, a subsequent subscriber causes
      two competing error signals to be sent, and one gets dropped and
      logged by reactor-core.
      
      This fix ensures that a rejection is raised in
      ReactorClientHttpResponse only after a cancel() was detected.
      
      Issue: SPR-17564
      7a5f8e03
  25. 23 11月, 2018 1 次提交
  26. 22 11月, 2018 4 次提交