f5c8c3d2aa
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://network.pivotal.io/open-source (301) with 1 occurrences migrated to: https://network.pivotal.io/open-source ([https](https://network.pivotal.io/open-source) result ReadTimeoutException). * [ ] http://03c7a684-6ff1-4bd0-ad45-d10374ffb2af:l5oq2q0unl35s6urfsuib0jvpo@192.168.0.81:15672/api/ (UnknownHostException) with 4 occurrences migrated to: https://03c7a684-6ff1-4bd0-ad45-d10374ffb2af:l5oq2q0unl35s6urfsuib0jvpo@192.168.0.81:15672/api/ ([https](https://03c7a684-6ff1-4bd0-ad45-d10374ffb2af:l5oq2q0unl35s6urfsuib0jvpo@192.168.0.81:15672/api/) result UnknownHostException). * [ ] http://a0f39f25-28a2-438e-a0e7-6c09d6d34dbd:1clgf5ipeop36437dmr2em4duk@192.168.1.55:15672/api/ (UnknownHostException) with 8 occurrences migrated to: https://a0f39f25-28a2-438e-a0e7-6c09d6d34dbd:1clgf5ipeop36437dmr2em4duk@192.168.1.55:15672/api/ ([https](https://a0f39f25-28a2-438e-a0e7-6c09d6d34dbd:1clgf5ipeop36437dmr2em4duk@192.168.1.55:15672/api/) result UnknownHostException). * [ ] http://foo.bar (UnknownHostException) with 20 occurrences migrated to: https://foo.bar ([https](https://foo.bar) result UnknownHostException). * [ ] http://username:password@192.168.0.90:1111/ (UnknownHostException) with 3 occurrences migrated to: https://username:password@192.168.0.90:1111/ ([https](https://username:password@192.168.0.90:1111/) result UnknownHostException). ## 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://redis.io/ with 1 occurrences migrated to: https://redis.io/ ([https](https://redis.io/) result 200). * [ ] http://redis.io/documentation with 1 occurrences migrated to: https://redis.io/documentation ([https](https://redis.io/documentation) result 200). * [ ] http://redis.io/topics/license with 1 occurrences migrated to: https://redis.io/topics/license ([https](https://redis.io/topics/license) result 200). * [ ] http://aspnetwebstack.codeplex.com/wikipage?title=Contributors with 1 occurrences migrated to: https://aspnetwebstack.codeplex.com/wikipage?title=Contributors ([https](https://aspnetwebstack.codeplex.com/wikipage?title=Contributors) result 301). # Ignored These URLs were intentionally ignored. * http://bar:11 with 3 occurrences * http://boo:222 with 4 occurrences * http://foo:11 with 3 occurrences * http://username:password@hostname:1111/ with 2 occurrences |
||
---|---|---|
config | ||
src | ||
test | ||
.appveyor.yml | ||
.gitattributes | ||
.gitignore | ||
.travis.yml | ||
CONTRIBUTING.md | ||
Connectors.sln | ||
License.txt | ||
README.md | ||
nuget.config | ||
open_source_licenses.txt | ||
stylecop.json | ||
targetframework.props | ||
versions.props |
README.md
.NET CloudFoundry Connectors
This repository contains several connectors which simplify the process of connecting to services on CloudFoundry.
.NET Runtime & Framework Support
The connectors are intended to support both .NET 4.6.1+ and .NET Core (CoreCLR/CoreFX) runtimes. Note that some connectors only support .NET 4.6.1+ since the libraries they depend on do not support .NET Core.
Where supported the connectors are built and unit tested on Windows, Linux and OSX.
While the primary usage of the connectors is intended to be with ASP.NET Core applications, they should also work fine with UWP, Console and ASP.NET 4.x apps.
Depending on their level of support, the connectors and samples have been tested on .NET Core 2.0, .NET 4.6.x, and on ASP.NET Core 2.0.
Usage
For more information on how to use these components see the online Steeltoe documentation.
Nuget Feeds
All new connector development is done on the dev branch. More stable versions of the connectors can be found on the master branch. The latest prebuilt packages from each branch can be found on one of two MyGet feeds. Released version can be found on nuget.org.
Building Pre-requisites
To build and run the unit tests:
- .NET Core SDK 2.0.3 or greater
- .NET Core Runtime 2.0.3
Building Packages & Running Tests - Windows
To build the packages on windows:
- git clone ...
- cd
<clone directory>
- cd src/
<project>
(e.g. cd src/Steeltoe.CloudFoundry.Connector) - dotnet restore
- dotnet pack --configuration
<Release or Debug>
The resulting artifacts can be found in the bin folder under the corresponding project. (e.g. src/Steeltoe.CloudFoundry.Connector\bin)
To run the unit tests:
- git clone ...
- cd
<clone directory>
- cd test/
<test project>
(e.g. cd test/Steeltoe.CloudFoundry.Connector.Test) - dotnet restore
- dotnet xunit -verbose
Building Packages & Running Tests - Linux/OSX
To build the packages on Linux/OSX: ( Note: Some connectors do not support CoreCLR.)
- git clone ...
- cd
<clone directory>
- cd src/
<project>
(e.g.. cd src/Steeltoe.CloudFoundry.Connector) - dotnet restore
- dotnet pack --configuration
<Release or Debug>
The resulting artifacts can be found in the bin folder under the corresponding project. (e.g. src/Steeltoe.CloudFoundry.Connector/bin
To run the unit tests: ( Note: Some connectors do not support CoreCLR.)
- git clone ...
- cd
<clone directory>
- cd test/
<test project>
(e.g. cd test/Steeltoe.CloudFoundry.Connector.Test) - dotnet restore
- dotnet xunit -verbose -framework netcoreapp2.0
Sample Applications
See the Samples repository for examples of how to use these packages.