anchor.diff:  ==== Configuring File System Watcher
   {sc-spring-boot-devtools}/filewatch/FileSystemWatcher.{sc-ext}[FileSystemWatcher] works
   by polling the class changes with a certain time interval, and then waiting for a
  -predefined quiet period to make sure no more changes are coming from the compiler. The
  -changes are then being uploaded to the remote application. On a slower development
  -environment, it may happen that the quiet period is not enough, and the changes in the
  -classes appear to be split into two batches. The server is then restarted after the first
  -batch of class changes is uploaded, but the second batch can’t immediately be sent to the
  -application, since the server is restarting.
  +predefined quiet period to make sure there are no more changes. The changes are then
  +uploaded to the remote application. On a slower development environment, it may happen
  +that the quiet period is not enough, and the changes in the classes may be split into batches.
  +The server is restarted after the first batch of class changes is uploaded.
  +The next batch can’t be sent to the application, since the server is restarting.
   
   This is typically manifested by a warning in the `RemoteSpringApplication` logs about
  -failing to upload some of the classes, and a consequent retry. But it may also lead to the
  +failing to upload some of the classes, and a consequent retry. But it may also lead to
   application code inconsistency and failure to restart after the first batch of changes is
   uploaded.
   
  
positive.code: 	spring.devtools.restart.quiet-period=1s
  ----
  
  The monitored classpath folders are now being swept every 2 seconds, and a 1 second quiet
  period is maintained to make sure no additional class changes are coming.
  
  [[security-configuration-for-devtools-remote]]
  ==== Security Configuration for Devtools Remote
  If you use security configuration on the server, you may observe HTTP error 401 or 403 in
  the logs of the `RemoteSpringApplication`:
  
  [indent=0,subs="attributes"]
  
negative.code: 
  	@Override
  	protected void configure(HttpSecurity http) throws Exception {
  		http.requestMatchers("/.~~spring-boot!~/restart").anyRequest().anonymous()
  			.and().csrf().disable();
  	}
  
  }
  ----
  
  NOTE: The above configuration will only affect the remote devtools endpoint. Spring Boot's default
  security auto-configuration will still apply to the rest of the application. If the rest
  of the application requires custom security, it needs to be configured separately.
  
  
  
  