From f6011997c849ebdc5545e90d7531f8ca03e6bc0a Mon Sep 17 00:00:00 2001 From: Spring Operator Date: Tue, 26 Mar 2019 13:09:53 -0700 Subject: [PATCH] URL Cleanup (#541) 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 But Review Recommended These URLs were fixed, but the https status was not OK. However, the https status was the same as the http request or http redirected to an https URL, so they were migrated. Your review is recommended. * [ ] http://www.puppycrawl.com/dtds/configuration_1_3.dtd (404) with 3 occurrences migrated to: https://www.puppycrawl.com/dtds/configuration_1_3.dtd ([https](https://www.puppycrawl.com/dtds/configuration_1_3.dtd) result 404). ## 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://12factor.net/ with 6 occurrences migrated to: https://12factor.net/ ([https](https://12factor.net/) result 200). * [ ] http://cloud.spring.io/spring-cloud-consul/ with 6 occurrences migrated to: https://cloud.spring.io/spring-cloud-consul/ ([https](https://cloud.spring.io/spring-cloud-consul/) result 200). * [ ] http://cloud.spring.io/spring-cloud-netflix/ with 6 occurrences migrated to: https://cloud.spring.io/spring-cloud-netflix/ ([https](https://cloud.spring.io/spring-cloud-netflix/) result 200). * [ ] http://cloud.spring.io/spring-cloud-zookeeper/ with 6 occurrences migrated to: https://cloud.spring.io/spring-cloud-zookeeper/ ([https](https://cloud.spring.io/spring-cloud-zookeeper/) result 200). * [ ] http://example.com with 6 occurrences migrated to: https://example.com ([https](https://example.com) result 200). * [ ] http://www.oracle.com/technetwork/java/javase/downloads/jce-6-download-429243.html with 12 occurrences migrated to: https://www.oracle.com/technetwork/java/javase/downloads/jce-6-download-429243.html ([https](https://www.oracle.com/technetwork/java/javase/downloads/jce-6-download-429243.html) result 200). * [ ] http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html with 12 occurrences migrated to: https://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html ([https](https://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html) result 200). * [ ] http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html with 12 occurrences migrated to: https://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html ([https](https://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html) result 200). * [ ] http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd with 1 occurrences migrated to: https://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd ([https](https://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd) result 200). * [ ] http://pivotal.io/platform-as-a-service/migrating-to-cloud-native-application-architectures-ebook with 6 occurrences migrated to: https://pivotal.io/platform-as-a-service/migrating-to-cloud-native-application-architectures-ebook ([https](https://pivotal.io/platform-as-a-service/migrating-to-cloud-native-application-architectures-ebook) result 301). * [ ] http://projects.spring.io/spring-boot with 6 occurrences migrated to: https://projects.spring.io/spring-boot ([https](https://projects.spring.io/spring-boot) result 301). # Ignored These URLs were intentionally ignored. * http://docbook.org/ns/docbook with 6 occurrences * http://localhost:8888 with 6 occurrences * http://stores with 3 occurrences * http://stores/stores with 14 occurrences * http://www.w3.org/1999/xlink with 6 occurrences * http://www.w3.org/2000/svg with 1 occurrences --- 1.0.x/checkstyle-checker.xml | 2 +- 1.0.x/spring-cloud-commons.xml | 20 ++++++++++---------- 1.2.x/spring-cloud-commons.xml | 20 ++++++++++---------- 1.3.x/spring-cloud-commons.xml | 20 ++++++++++---------- 2.0.x/checkstyle-checker.xml | 2 +- 2.0.x/spring-cloud-commons.xml | 20 ++++++++++---------- 2.1.x/spring-cloud-commons.xml | 22 +++++++++++----------- checkstyle-checker.xml | 2 +- font-awesome/font/fontawesome-webfont.svg | 2 +- spring-cloud-commons.xml | 22 +++++++++++----------- 10 files changed, 66 insertions(+), 66 deletions(-) diff --git a/1.0.x/checkstyle-checker.xml b/1.0.x/checkstyle-checker.xml index 79233ddb..ce80589e 100644 --- a/1.0.x/checkstyle-checker.xml +++ b/1.0.x/checkstyle-checker.xml @@ -1,7 +1,7 @@ + "https://www.puppycrawl.com/dtds/configuration_1_3.dtd"> diff --git a/1.0.x/spring-cloud-commons.xml b/1.0.x/spring-cloud-commons.xml index 72006cae..7ad796c5 100644 --- a/1.0.x/spring-cloud-commons.xml +++ b/1.0.x/spring-cloud-commons.xml @@ -8,18 +8,18 @@ -Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. A related discipline is that of building 12-factor Apps in which development practices are aligned with delivery and operations goals, for instance by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways and the starting point is a set of features that all components in a distributed system either need or need easy access to when required. -Many of those features are covered by Spring Boot, which we build on in Spring Cloud. Some more are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (eg. Spring Cloud Netflix vs. Spring Cloud Consul). +Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. A related discipline is that of building 12-factor Apps in which development practices are aligned with delivery and operations goals, for instance by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways and the starting point is a set of features that all components in a distributed system either need or need easy access to when required. +Many of those features are covered by Spring Boot, which we build on in Spring Cloud. Some more are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (eg. Spring Cloud Netflix vs. Spring Cloud Consul). If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information: -Java 6 JCE +Java 6 JCE -Java 7 JCE +Java 7 JCE -Java 8 JCE +Java 8 JCE Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using). @@ -298,13 +298,13 @@ the full strength JCE extensions in your JVM. If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information: -Java 6 JCE +Java 6 JCE -Java 7 JCE +Java 7 JCE -Java 8 JCE +Java 8 JCE Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using). @@ -333,7 +333,7 @@ the full strength JCE extensions in your JVM. Patterns such as service discovery, load balancing and circuit breakers lend themselves to a common abstraction layer that can be consumed by all Spring Cloud clients, independent of the implementation (e.g. discovery via Eureka or Consul).
@EnableDiscoveryClient -Commons provides the @EnableDiscoveryClient annotation. This looks for implementations of the DiscoveryClient interface via META-INF/spring.factories. Implementations of Discovery Client will add a configuration class to spring.factories under the org.springframework.cloud.client.discovery.EnableDiscoveryClient key. Examples of DiscoveryClient implementations: are Spring Cloud Netflix Eureka, Spring Cloud Consul Discovery and Spring Cloud Zookeeper Discovery. +Commons provides the @EnableDiscoveryClient annotation. This looks for implementations of the DiscoveryClient interface via META-INF/spring.factories. Implementations of Discovery Client will add a configuration class to spring.factories under the org.springframework.cloud.client.discovery.EnableDiscoveryClient key. Examples of DiscoveryClient implementations: are Spring Cloud Netflix Eureka, Spring Cloud Consul Discovery and Spring Cloud Zookeeper Discovery. By default, implementations of DiscoveryClient will auto-register the local Spring Boot server with the remote discovery server. This can be disabled by setting autoRegister=false in @EnableDiscoveryClient.
Health Indicator @@ -451,7 +451,7 @@ public class MyClass { } public String doStuff() { - return restTemplate.getForObject("http://example.com", String.class); + return restTemplate.getForObject("https://example.com", String.class); } } diff --git a/1.2.x/spring-cloud-commons.xml b/1.2.x/spring-cloud-commons.xml index 8a52aa74..68d553bd 100644 --- a/1.2.x/spring-cloud-commons.xml +++ b/1.2.x/spring-cloud-commons.xml @@ -8,18 +8,18 @@ -Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. A related discipline is that of building 12-factor Apps in which development practices are aligned with delivery and operations goals, for instance by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways and the starting point is a set of features that all components in a distributed system either need or need easy access to when required. -Many of those features are covered by Spring Boot, which we build on in Spring Cloud. Some more are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (eg. Spring Cloud Netflix vs. Spring Cloud Consul). +Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. A related discipline is that of building 12-factor Apps in which development practices are aligned with delivery and operations goals, for instance by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways and the starting point is a set of features that all components in a distributed system either need or need easy access to when required. +Many of those features are covered by Spring Boot, which we build on in Spring Cloud. Some more are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (eg. Spring Cloud Netflix vs. Spring Cloud Consul). If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information: -Java 6 JCE +Java 6 JCE -Java 7 JCE +Java 7 JCE -Java 8 JCE +Java 8 JCE Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using). @@ -298,13 +298,13 @@ the full strength JCE extensions in your JVM. If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information: -Java 6 JCE +Java 6 JCE -Java 7 JCE +Java 7 JCE -Java 8 JCE +Java 8 JCE Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using). @@ -333,7 +333,7 @@ the full strength JCE extensions in your JVM. Patterns such as service discovery, load balancing and circuit breakers lend themselves to a common abstraction layer that can be consumed by all Spring Cloud clients, independent of the implementation (e.g. discovery via Eureka or Consul).
@EnableDiscoveryClient -Commons provides the @EnableDiscoveryClient annotation. This looks for implementations of the DiscoveryClient interface via META-INF/spring.factories. Implementations of Discovery Client will add a configuration class to spring.factories under the org.springframework.cloud.client.discovery.EnableDiscoveryClient key. Examples of DiscoveryClient implementations: are Spring Cloud Netflix Eureka, Spring Cloud Consul Discovery and Spring Cloud Zookeeper Discovery. +Commons provides the @EnableDiscoveryClient annotation. This looks for implementations of the DiscoveryClient interface via META-INF/spring.factories. Implementations of Discovery Client will add a configuration class to spring.factories under the org.springframework.cloud.client.discovery.EnableDiscoveryClient key. Examples of DiscoveryClient implementations: are Spring Cloud Netflix Eureka, Spring Cloud Consul Discovery and Spring Cloud Zookeeper Discovery. By default, implementations of DiscoveryClient will auto-register the local Spring Boot server with the remote discovery server. This can be disabled by setting autoRegister=false in @EnableDiscoveryClient.
@@ -447,7 +447,7 @@ public class MyClass { } public String doStuff() { - return restTemplate.getForObject("http://example.com", String.class); + return restTemplate.getForObject("https://example.com", String.class); } } diff --git a/1.3.x/spring-cloud-commons.xml b/1.3.x/spring-cloud-commons.xml index 800917d4..19feb7f2 100644 --- a/1.3.x/spring-cloud-commons.xml +++ b/1.3.x/spring-cloud-commons.xml @@ -8,18 +8,18 @@ -Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. A related discipline is that of building 12-factor Apps in which development practices are aligned with delivery and operations goals, for instance by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways and the starting point is a set of features that all components in a distributed system either need or need easy access to when required. -Many of those features are covered by Spring Boot, which we build on in Spring Cloud. Some more are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (eg. Spring Cloud Netflix vs. Spring Cloud Consul). +Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. A related discipline is that of building 12-factor Apps in which development practices are aligned with delivery and operations goals, for instance by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways and the starting point is a set of features that all components in a distributed system either need or need easy access to when required. +Many of those features are covered by Spring Boot, which we build on in Spring Cloud. Some more are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (eg. Spring Cloud Netflix vs. Spring Cloud Consul). If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information: -Java 6 JCE +Java 6 JCE -Java 7 JCE +Java 7 JCE -Java 8 JCE +Java 8 JCE Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using). @@ -305,13 +305,13 @@ the full strength JCE extensions in your JVM. If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information: -Java 6 JCE +Java 6 JCE -Java 7 JCE +Java 7 JCE -Java 8 JCE +Java 8 JCE Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using). @@ -344,7 +344,7 @@ will also be disabled since they are just a special case of /restartPatterns such as service discovery, load balancing and circuit breakers lend themselves to a common abstraction layer that can be consumed by all Spring Cloud clients, independent of the implementation (e.g. discovery via Eureka or Consul).
@EnableDiscoveryClient -Commons provides the @EnableDiscoveryClient annotation. This looks for implementations of the DiscoveryClient interface via META-INF/spring.factories. Implementations of Discovery Client will add a configuration class to spring.factories under the org.springframework.cloud.client.discovery.EnableDiscoveryClient key. Examples of DiscoveryClient implementations: are Spring Cloud Netflix Eureka, Spring Cloud Consul Discovery and Spring Cloud Zookeeper Discovery. +Commons provides the @EnableDiscoveryClient annotation. This looks for implementations of the DiscoveryClient interface via META-INF/spring.factories. Implementations of Discovery Client will add a configuration class to spring.factories under the org.springframework.cloud.client.discovery.EnableDiscoveryClient key. Examples of DiscoveryClient implementations: are Spring Cloud Netflix Eureka, Spring Cloud Consul Discovery and Spring Cloud Zookeeper Discovery. By default, implementations of DiscoveryClient will auto-register the local Spring Boot server with the remote discovery server. This can be disabled by setting autoRegister=false in @EnableDiscoveryClient. The use of @EnableDiscoveryClient is no longer required. It is enough to just have a DiscoveryClient implementation @@ -526,7 +526,7 @@ public class MyClass { } public String doStuff() { - return restTemplate.getForObject("http://example.com", String.class); + return restTemplate.getForObject("https://example.com", String.class); } } diff --git a/2.0.x/checkstyle-checker.xml b/2.0.x/checkstyle-checker.xml index 79233ddb..ce80589e 100644 --- a/2.0.x/checkstyle-checker.xml +++ b/2.0.x/checkstyle-checker.xml @@ -1,7 +1,7 @@ + "https://www.puppycrawl.com/dtds/configuration_1_3.dtd"> diff --git a/2.0.x/spring-cloud-commons.xml b/2.0.x/spring-cloud-commons.xml index 99021688..ba64ac3c 100644 --- a/2.0.x/spring-cloud-commons.xml +++ b/2.0.x/spring-cloud-commons.xml @@ -8,18 +8,18 @@ -Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. A related discipline is that of building 12-factor Apps in which development practices are aligned with delivery and operations goals, for instance by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways and the starting point is a set of features that all components in a distributed system either need or need easy access to when required. -Many of those features are covered by Spring Boot, which we build on in Spring Cloud. Some more are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (eg. Spring Cloud Netflix vs. Spring Cloud Consul). +Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. A related discipline is that of building 12-factor Apps in which development practices are aligned with delivery and operations goals, for instance by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways and the starting point is a set of features that all components in a distributed system either need or need easy access to when required. +Many of those features are covered by Spring Boot, which we build on in Spring Cloud. Some more are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (eg. Spring Cloud Netflix vs. Spring Cloud Consul). If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information: -Java 6 JCE +Java 6 JCE -Java 7 JCE +Java 7 JCE -Java 8 JCE +Java 8 JCE Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using). @@ -298,13 +298,13 @@ the full strength JCE extensions in your JVM. If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information: -Java 6 JCE +Java 6 JCE -Java 7 JCE +Java 7 JCE -Java 8 JCE +Java 8 JCE Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using). @@ -333,7 +333,7 @@ the full strength JCE extensions in your JVM. Patterns such as service discovery, load balancing and circuit breakers lend themselves to a common abstraction layer that can be consumed by all Spring Cloud clients, independent of the implementation (e.g. discovery via Eureka or Consul).
@EnableDiscoveryClient -Commons provides the @EnableDiscoveryClient annotation. This looks for implementations of the DiscoveryClient interface via META-INF/spring.factories. Implementations of Discovery Client will add a configuration class to spring.factories under the org.springframework.cloud.client.discovery.EnableDiscoveryClient key. Examples of DiscoveryClient implementations: are Spring Cloud Netflix Eureka, Spring Cloud Consul Discovery and Spring Cloud Zookeeper Discovery. +Commons provides the @EnableDiscoveryClient annotation. This looks for implementations of the DiscoveryClient interface via META-INF/spring.factories. Implementations of Discovery Client will add a configuration class to spring.factories under the org.springframework.cloud.client.discovery.EnableDiscoveryClient key. Examples of DiscoveryClient implementations: are Spring Cloud Netflix Eureka, Spring Cloud Consul Discovery and Spring Cloud Zookeeper Discovery. By default, implementations of DiscoveryClient will auto-register the local Spring Boot server with the remote discovery server. This can be disabled by setting autoRegister=false in @EnableDiscoveryClient. The use of @EnableDiscoveryClient is no longer required. It is enough to just have a DiscoveryClient implementation @@ -469,7 +469,7 @@ public class MyClass { } public String doStuff() { - return restTemplate.getForObject("http://example.com", String.class); + return restTemplate.getForObject("https://example.com", String.class); } } diff --git a/2.1.x/spring-cloud-commons.xml b/2.1.x/spring-cloud-commons.xml index bb39e03a..3c60a9de 100644 --- a/2.1.x/spring-cloud-commons.xml +++ b/2.1.x/spring-cloud-commons.xml @@ -8,23 +8,23 @@ -Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. -A related discipline is that of building 12-factor Applications, in which development practices are aligned with delivery and operations goals — for instance, by using declarative programming and management and monitoring. +Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. +A related discipline is that of building 12-factor Applications, in which development practices are aligned with delivery and operations goals — for instance, by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways. The starting point is a set of features to which all components in a distributed system need easy access. -Many of those features are covered by Spring Boot, on which Spring Cloud builds. Some more features are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. +Many of those features are covered by Spring Boot, on which Spring Cloud builds. Some more features are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope, and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (such as Spring Cloud Netflix and Spring Cloud Consul). If you get an exception due to "Illegal key size" and you use Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information: -Java 6 JCE +Java 6 JCE -Java 7 JCE +Java 7 JCE -Java 8 JCE +Java 8 JCE Extract the files into the JDK/jre/lib/security folder for whichever version of JRE/JDK x64/x86 you use. @@ -227,13 +227,13 @@ To use the encryption features in an application, you need to include Spring Sec See the following links for more information: -Java 6 JCE +Java 6 JCE -Java 7 JCE +Java 7 JCE -Java 8 JCE +Java 8 JCE Extract the files into the JDK/jre/lib/security folder for whichever version of JRE/JDK x64/x86 you use. @@ -269,7 +269,7 @@ will also be disabled since they are just a special case of /actuator/r Spring Cloud Commons provides the @EnableDiscoveryClient annotation. This looks for implementations of the DiscoveryClient interface with META-INF/spring.factories. Implementations of the Discovery Client add a configuration class to spring.factories under the org.springframework.cloud.client.discovery.EnableDiscoveryClient key. -Examples of DiscoveryClient implementations include Spring Cloud Netflix Eureka, Spring Cloud Consul Discovery, and Spring Cloud Zookeeper Discovery. +Examples of DiscoveryClient implementations include Spring Cloud Netflix Eureka, Spring Cloud Consul Discovery, and Spring Cloud Zookeeper Discovery. By default, implementations of DiscoveryClient auto-register the local Spring Boot server with the remote discovery server. This behavior can be disabled by setting autoRegister=false in @EnableDiscoveryClient. @@ -508,7 +508,7 @@ public class MyClass { } public String doStuff() { - return restTemplate.getForObject("http://example.com", String.class); + return restTemplate.getForObject("https://example.com", String.class); } } diff --git a/checkstyle-checker.xml b/checkstyle-checker.xml index 79233ddb..ce80589e 100644 --- a/checkstyle-checker.xml +++ b/checkstyle-checker.xml @@ -1,7 +1,7 @@ + "https://www.puppycrawl.com/dtds/configuration_1_3.dtd"> diff --git a/font-awesome/font/fontawesome-webfont.svg b/font-awesome/font/fontawesome-webfont.svg index 2edb4ec3..8b349d50 100755 --- a/font-awesome/font/fontawesome-webfont.svg +++ b/font-awesome/font/fontawesome-webfont.svg @@ -1,5 +1,5 @@ - + diff --git a/spring-cloud-commons.xml b/spring-cloud-commons.xml index e550a66e..9a2f8c49 100644 --- a/spring-cloud-commons.xml +++ b/spring-cloud-commons.xml @@ -8,23 +8,23 @@ -Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. -A related discipline is that of building 12-factor Applications, in which development practices are aligned with delivery and operations goals — for instance, by using declarative programming and management and monitoring. +Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. +A related discipline is that of building 12-factor Applications, in which development practices are aligned with delivery and operations goals — for instance, by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways. The starting point is a set of features to which all components in a distributed system need easy access. -Many of those features are covered by Spring Boot, on which Spring Cloud builds. Some more features are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. +Many of those features are covered by Spring Boot, on which Spring Cloud builds. Some more features are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope, and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (such as Spring Cloud Netflix and Spring Cloud Consul). If you get an exception due to "Illegal key size" and you use Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information: -Java 6 JCE +Java 6 JCE -Java 7 JCE +Java 7 JCE -Java 8 JCE +Java 8 JCE Extract the files into the JDK/jre/lib/security folder for whichever version of JRE/JDK x64/x86 you use. @@ -227,13 +227,13 @@ To use the encryption features in an application, you need to include Spring Sec See the following links for more information: -Java 6 JCE +Java 6 JCE -Java 7 JCE +Java 7 JCE -Java 8 JCE +Java 8 JCE Extract the files into the JDK/jre/lib/security folder for whichever version of JRE/JDK x64/x86 you use. @@ -269,7 +269,7 @@ will also be disabled since they are just a special case of /actuator/r Spring Cloud Commons provides the @EnableDiscoveryClient annotation. This looks for implementations of the DiscoveryClient interface with META-INF/spring.factories. Implementations of the Discovery Client add a configuration class to spring.factories under the org.springframework.cloud.client.discovery.EnableDiscoveryClient key. -Examples of DiscoveryClient implementations include Spring Cloud Netflix Eureka, Spring Cloud Consul Discovery, and Spring Cloud Zookeeper Discovery. +Examples of DiscoveryClient implementations include Spring Cloud Netflix Eureka, Spring Cloud Consul Discovery, and Spring Cloud Zookeeper Discovery. By default, implementations of DiscoveryClient auto-register the local Spring Boot server with the remote discovery server. This behavior can be disabled by setting autoRegister=false in @EnableDiscoveryClient. @@ -508,7 +508,7 @@ public class MyClass { } public String doStuff() { - return restTemplate.getForObject("http://example.com", String.class); + return restTemplate.getForObject("https://example.com", String.class); } }