1. Enabling Production-ready Features ..... 300 13.2. Endpoints ..... 300 13.2.1. Enabling Endpoints ..... 302 13.2.2. Exposing Endpoints ..... 303 13.2.3. Security ..... 305 Cross Site Request 307 13.2.4. Configuring Endpoints ..... 307 13.2.5. Hypermedia for Actuator Web Endpoints ..... 308 13.2.6. CORS Support ..... 308 13.2.7. Implementing Custom Endpoints ..... 309 Receiving Receiving Input ..... 309 Custom Web Endpoints ..... 310 Servlet Endpoints ..... 312 Controller Endpoints ..... 312 13.2.8. Health Information ..... 312 Auto-configured HealthIndicators

Integration Version 5.3.36-SNAPSHOT ## Table of Contents 1. REST Endpoints ..... 2 1.1. RestTemplate ..... 2 1.1.1. Initialization ..... 3 URIs ..... 3 Headers ..... 4 1.1.2. Body ..... 4 Messages Within Transactions ..... 43 4.4. Support for JCA Message Endpoints ..... 44 4.5. Annotation-driven Listener Endpoints ..... 46 4.5.1. Enable Listener Endpoint Annotations ..... 47 4.5 integration with a number of technologies. ### Chapter 1. REST Endpoints The Spring Framework provides two choices for making calls to REST endpoints: • RestTemplate: The original Spring REST client with a

... 297 8.2. Endpoints ..... 297 8.2.1. Enabling Endpoints ..... 299 8.2.2. Exposing Endpoints ..... 300 8.2.3. Securing HTTP Endpoints ..... 302 8.2.4. Configuring Endpoints ..... 304 8.2 Actuator Web Endpoints ..... 305 8.2.6. CORS Support ..... 305 8.2.7. Implementing Custom Endpoints ..... 306 Receiving Input ..... 306 Custom Web Endpoints ..... 307 Servlet Endpoints ..... 309 309 Controller Endpoints ..... 309 8.2.8. Health Information ..... 309 Auto-configured HealthIndicators ..... 310 Writing Custom HealthIndicators ..... 311 Reactive Health Indicators ..... 313

Managing Exceptions 64 REST API exceptions 65 1.4.7. Controller Advice 66 1.5. Functional Endpoints 67 1.5.1. Overview 67 1.5.2. HandlerFunction 69 ServerRequest 70 ServerResponse 71 Handler asynchronous logic. At the programming-model level, Java 8 enabled Spring WebFlux to offer functional web endpoints alongside annotated controllers. ##### 1.1.1. Define "Reactive" We touched on “non-blocking” notable difference is that WebFlux also supports reactive @RequestBody arguments. - Functional Endpoints: Lambda-based, lightweight, and functional programming model. You can think of this as a small library

170 49. Endpoints ..... 171 49.1. Customizing endpoints ..... 172 49.2. Hypermedia for actuator MVC endpoints ..... 173 49.3. CORS support ..... 173 49.4. Adding custom endpoints ..... 173 InfoContributors ..... 177 50. Monitoring and management over HTTP ..... 179 50.1. Accessing sensitive endpoints ..... 179 50.2. Customizing the management endpoint paths ..... 180 50.3. Customizing the management SSL ..... 181 50.5. Customizing the management server address ..... 181 50.6. Disabling HTTP endpoints ..... 181 50.7. HTTP health endpoint format and access restrictions ..... 181 51. Monitoring

production-ready features 47. Endpoints Customizing endpoints Hypermedia for actuator MVC endpoints CORS support Adding custom endpoints Health information Writing custom InfoContributors 48. Monitoring and management over HTTP Accessing sensitive endpoints Customizing the management endpoint paths Customizing the management server port Disabling HTTP endpoints HTTP health endpoint format and access restrictions 49. Monitoring and management over JMX Customizing MBean names Disabling JMX endpoints Using Jolokia

45. Enabling production-ready features 46. Endpoints Customizing endpoints Hypermedia for actuator MVC endpoints CORS support Adding custom endpoints Health information Security with HealthIndicators sensitive endpoints Customizing the management endpoint paths Customizing the management server port Configuring management-specific SSL Customizing the management server address Disabling HTTP endpoints HTTP access restrictions 48. Monitoring and management over JMX Customizing MBean names Disabling JMX endpoints Using Jolokia for JMX over HTTP Customizing Jolokia Disabling Jolokia 49. Monitoring and management

"api_name": "cn", "is_master": "true", #作为 master Region "endpoints": [ "http://host1.ceph.work80/ ], "hostnames": [ "master_zone": "zones": [ { "name": "cn-zone1", "endpoints": [ "http://host1.ceph.work80/ ], "log_meta": "bucket_index_max_shards": 8 #bucket 分片数量 }, "name": "us-zone1", "endpoints": [ "http://host2.ceph.work80/ ], "log_meta": "true", "log_data":

: has no endpoints" -m tcp --dport 80 -j REJECT --reject-with icmp-port-unreachable -A KUBE-SERVICES -d 10.96.61.252/32 -p tcp -m comment --comment "default/nginx-64: has no endpoints" -m tcp 7: has no endpoints" -m tcp --dport 80 -j REJECT --reject-with icmp-port-unreachable -A KUBE-SERVICES -d 10.98.85.41/32 -p tcp -m comment --comment "default/nginx-9: has no endpoints" -m tcp : has no endpoints" -m tcp --dport 80 -j REJECT --reject-with icmp-port-unreachable -A KUBE-SERVICES -d 10.106.49.80/32 -p tcp -m comment --comment "default/nginx-37: has no endpoints" -m tcp

production-ready features 47. Endpoints Customizing endpoints Hypermedia for actuator MVC endpoints CORS support Adding custom endpoints Health information Security Writing custom InfoContributors 48. Monitoring and management over HTTP Accessing sensitive endpoints Customizing the management endpoint paths Customizing the management server port Configuring address Disabling HTTP endpoints HTTP health endpoint format and access restrictions 49. Monitoring and management over JMX Customizing MBean names Disabling JMX endpoints Using Jolokia for JMX over