Files
spring-cloud-dataflow-samples/dataflow-zuul
Spring Operator 2d40a251fe URL Cleanup
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/ with 4 occurrences migrated to:
  https://www.apache.org/licenses/ ([https](https://www.apache.org/licenses/) result 200).
* [ ] http://www.apache.org/licenses/LICENSE-2.0 with 27 occurrences migrated to:
  https://www.apache.org/licenses/LICENSE-2.0 ([https](https://www.apache.org/licenses/LICENSE-2.0) result 200).
2019-08-07 12:09:13 +05:30
..
2019-08-07 12:09:13 +05:30
2019-08-07 12:09:13 +05:30
2019-03-18 23:13:31 +05:30
2019-08-07 11:19:05 +05:30
2019-02-19 16:41:55 -10:00

= 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`