anchor.diff:  
   Note the use of the "spring-cloud-starter-zuul" - it's a starter POM just like the Spring Boot ones, but it governs the dependencies we need for this Zuul proxy. We are also using `&lt;dependencyManagement&gt;` because we want to be able to depend on all the versions of transitive dependencies being correct.
   
  -=== Consuming the Proxy in the Client
  +//=== Consuming the Proxy in the Client
  +=== プロキシを使うクライアント
   
   With those changes in place our application still works, but we haven't actually used the new proxy yet until we modify the client. Fortunately that's trivial. We just need to go from this implementation of the "home" controller:
   
  
positive.code: 
  Now when we fire up the servers everything is working and the requests are being proxied through the UI (API Gateway) to the resource server.
  
  === Further Simplifications
  
  Even better: we don't need the CORS filter any more in the resource server. We threw that one together pretty quickly anyway, and it should have been a red light that we had to do anything as technically focused by hand (especially where it concerns security). Fortunately it is now redundant, so we can just throw it away, and go back to sleeping at night!
  
  == Securing the Resource Server
  
  You might remember in the intermediate state that we started from there is no security in place for the resource server. 
  
  
negative.code: 
  As long as redis is still running in the background (use the https://github.com/dsyer/spring-security-angular/tree/master/proxy/fig.yml[`fig.yml`] if you like to start it) then the system will work. Load the homepage for the UI at http://localhost:8080[http://localhost:8080] and login and you will see the message from the backend rendered on the homepage.
  
  //== How Does it Work?
  == どうやって動いているの?
  
  What is going on behind the scenes now? First we can look at the HTTP requests in the UI server (and API Gateway):
  
  