as Publisher) can produce data that an HTTP server (acting as Subscriber) can then write to the response. The 2 main purpose of Reactive Streams is to let the subscriber control how quickly or how slowly deserialization of HTTP request and response content. 1.2.1. HttpHandler HttpHandler is a simple contract with a single method to handle a request and a response. It is intentionally minimal, and its ResponseStatusExceptionHandler Provides handling for exceptions of type ResponseStatusException by setting the response to the HTTP status code of the exception. WebFluxResponseStatusException Handler Extension of

logical String-based view names returned from a handler to an actual View with which to render to the response. See View Resolution and View Technologies. LocaleResolver, LocaleContextResolver Resolve the controllers) is run to prepare a model for rendering. Alternatively, for annotated controllers, the response can be rendered (within the HandlerAdapter) instead of returning a view. • If a model is returned as any others. By default, this is set to false, in which case the DispatcherServlet sets the response status to 404 (NOT_FOUND) without raising an exception. Note that, if default servlet handling

parameters with @RequestParam Mapping the request body with the @RequestBody annotation Mapping the response body with the @ResponseBody annotation Creating REST Controllers with the @RestController annotation HTTP caching support for static resources Support for the Cache-Control, ETag and Last-Modified response headers in Controllers Shallow ETag support Code-based Servlet container initialization Configuring Accessing RESTful services on the client RestTemplate Working with the URI Dealing with request and response headers Jackson JSON Views support HTTP message conversion StringHttpMessageConverter FormHttpMessageConverter

parameters with @RequestParam Mapping the request body with the @RequestBody annotation Mapping the response body with the @ResponseBody annotation Creating REST Controllers with the @RestController annotation HTTP caching support for static resources Support for the Cache-Control, ETag and Last-Modified response headers in Controllers Shallow ETag support Code-based Servlet container initialization Configuring Accessing RESTful services on the Client RestTemplate Working with the URI Dealing with request and response headers Jackson JSON Views support HTTP Message Conversion StringHttpMessageConverter FormHttpMessageConverter

503 Mapping the request body with the @RequestBody annotation .................. 504 Mapping the response body with the @ResponseBody annotation ............. 505 Spring Framework Reference Documentation ..................................... 547 Support for the Cache-Control, ETag and Last-Modified response headers in Controllers ........................................................................ .................................................................. 687 Dealing with request and response headers ............................................. 688 Jackson JSON Views support .........

496 Mapping the request body with the @RequestBody annotation .................. 497 Mapping the response body with the @ResponseBody annotation ............. 498 Creating REST Controllers with the @RestController ..................................... 539 Support for the Cache-Control, ETag and Last-Modified response headers in Controllers ........................................................................ .................................................................. 677 Dealing with request and response headers ............................................. 678 Jackson JSON Views support .........

Custom Web Endpoints Web Endpoint Request Predicates Path HTTP method Consumes Produces Web Endpoint Response Status Web Endpoint Range Requests Web Endpoint Security Servlet endpoints Controller endpoints Change the HTTP Port Use a Random Unassigned HTTP Port Discover the HTTP Port at Runtime Enable HTTP Response Compression Configure SSL Configure HTTP/2 HTTP/2 with Undertow HTTP/2 with Jetty HTTP/2 with Tomcat This will give you information about the incoming request, which handler is processing it, the response outcome, etc. If you wish to log all request details (including potentially sensitive information)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 4.5.4. Response Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . POST and returns the Location header from the response. postForObject Creates a new resource by using POST and returns the representation from the response. postForEntity Creates a new resource by using representation from the response. put Creates or updates a resource by using PUT. patchForObject Updates a resource by using PATCH and returns the representation from the response. Note that the JDK HttpURLConnection

Custom Web Endpoints Web Endpoint Request Predicates Path HTTP method Consumes Produces Web Endpoint Response Status Web Endpoint Range Requests Web Endpoint Security Servlet endpoints Controller endpoints Change the HTTP Port Use a Random Unassigned HTTP Port Discover the HTTP Port at Runtime Enable HTTP Response Compression Configure SSL Configure HTTP/2 HTTP/2 with Undertow HTTP/2 with Jetty HTTP/2 with Tomcat This will give you information about the incoming request, which handler is processing it, the response outcome, etc. If you wish to log all request details (including potentially sensitive information)

Custom Web Endpoints Web Endpoint Request Predicates Path HTTP method Consumes Produces Web Endpoint Response Status Web Endpoint Range Requests Web Endpoint Security Servlet endpoints Controller endpoints Change the HTTP Port Use a Random Unassigned HTTP Port Discover the HTTP Port at Runtime Enable HTTP Response Compression Configure SSL Configure HTTP/2 HTTP/2 with Undertow HTTP/2 with Jetty HTTP/2 with Tomcat This will give you information about the incoming request, which handler is processing it, the response outcome, etc. If you wish to log all request details (including potentially sensitive information)