3beaa76088
This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener). # Fixed URLs ## Fixed Success These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended. * http://www.apache.org/licenses/LICENSE-2.0 migrated to: https://www.apache.org/licenses/LICENSE-2.0 ([https](https://www.apache.org/licenses/LICENSE-2.0) result 200). * http://repo.spring.io/libs-milestone-local migrated to: https://repo.spring.io/libs-milestone-local ([https](https://repo.spring.io/libs-milestone-local) result 302). * http://repo.spring.io/milestone migrated to: https://repo.spring.io/milestone ([https](https://repo.spring.io/milestone) result 302). * http://repo.spring.io/snapshot migrated to: https://repo.spring.io/snapshot ([https](https://repo.spring.io/snapshot) result 302). # Ignored These URLs were intentionally ignored. * http://localhost:7577/login * http://localhost:8080/uaa * http://localhost:9393/login * http://maven.apache.org/POM/4.0.0 * http://maven.apache.org/xsd/maven-4.0.0.xsd * http://www.w3.org/2001/XMLSchema-instance
= Data Flow Zuul Proxy Example This example provides an example of using the Spring Cloud Data Flow Server behind a Zuul proxy server. The Zuul proxy server will start on port `8080`. When you go to `http://localhost:8080/dashboard` you will see that all Dashboard requests will be proxied over to port `9393`. Please make sure that you start Spring Cloud Data Flow Server with the property `server.use-forward-headers` and the value `true`. In order to get everything running we need to setup the following server instances: * Spring Cloud Skipper (port `7577`) * Spring Cloud Data Flow (port `9393`) == Build + Run Build the sample using `$ mvn clean package` and run using `$ java -jar target/dataflow-zuul-1.0.0.BUILD-SNAPSHOT.jar`