anchor.diff:  
   
   [[webflux-logging-sensitive-data]]
  -==== Logging Sensitive Data
  +==== Sensitive Data
   [.small]#<<web.adoc#mvc-logging-sensitive-data,Same as in Spring MVC>>#
   
   `DEBUG` and `TRACE` logging can log sensitive information. This is why form parameters and
  
positive.code: 		// ...
  	}
  ----
  <1>
  ====
  
  Spring WebFlux, unlike Spring MVC, supports reactive types in the model -- for example,
  
negative.code: [[webflux-reactive-spring-web]]
  == Reactive Core
  
  The `spring-web` module contains the following foundational support for reactive web
  applications:
  
  * For server request processing there are two levels of support.
  ** <<webflux-httphandler,HttpHandler>>: Basic contract for HTTP request handling with
  non-blocking I/O and Reactive Streams back pressure, along with adapters for Reactor Netty,
  Undertow, Tomcat, Jetty, and any Servlet 3.1+ container.
  ** <<webflux-web-handler-api>>: Slightly higher level, general-purpose web API for
  request handling, on top of which concrete programming models such as annotated
  controllers and functional endpoints are built.
  * For the client side, there is a basic `ClientHttpConnector` contract to perform HTTP
  requests with non-blocking I/O and Reactive Streams back pressure, along with adapters for
  https://github.com/reactor/reactor-netty[Reactor Netty] and for the reactive
  https://github.com/jetty-project/jetty-reactive-httpclient[Jetty HtpClient].
  The higher level <<web-reactive.adoc#webflux-client,WebClient>> used in applications
  builds on this basic contract.
  * For client and server, <<webflux-codecs,codecs>> to use to serialize and
  deserialize HTTP request and response content.
  
  
  
  