Skip to content

Commit

Permalink
Fix readme
Browse files Browse the repository at this point in the history
  • Loading branch information
kfrancis committed Apr 28, 2016
1 parent 113410f commit 26ef266
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,8 @@
# Chargify.NET [![Build status](https://ci.appveyor.com/api/projects/status/76aex0a2h6j63g5x/branch/master?svg=true)](https://ci.appveyor.com/project/kfrancis/chargify-dot-net/branch/master)
# Chargify.NET [![Build status](https://ci.appveyor.com/api/projects/status/76aex0a2h6j63g5x/branch/master?svg=true)](https://ci.appveyor.com/project/kfrancis/chargify-dot-net/branch/master)[![Join the chat at https://gitter.im/kfrancis/chargify-dot-net](https://badges.gitter.im/kfrancis/chargify-dot-net.svg)](https://gitter.im/kfrancis/chargify-dot-net?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)

[![Join the chat at https://gitter.im/kfrancis/chargify-dot-net](https://badges.gitter.im/kfrancis/chargify-dot-net.svg)](https://gitter.im/kfrancis/chargify-dot-net?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
_A comprehensive C# API wrapper library for accessing [chargify.com](http://www.chargify.com), using XML or JSON to read/write._

* Chargify.NET: [![NuGet downloads](https://img.shields.io/nuget/dt/chargify.svg)](http://www.nuget.org/packages/chargify) [![NuGet version](https://img.shields.io/nuget/v/chargify.svg)](http://www.nuget.org/packages/chargify)
* Chargify.NET: [![NuGet version](https://img.shields.io/nuget/v/chargify.svg)](http://www.nuget.org/packages/chargify)

## Important SSLv3/POODLE
To correct the error "Could not create SSL/TLS secure channel", update to at least version [1.1.5400.37999](https://www.nuget.org/packages/chargify/) either through the downloads or (recommended) through nuget. I *HIGHLY* recommend using nuget as I release changes through there very often. For more information, see the Chargify blog post ["Dropping support for SSLv3 - may cause API connection problems"](https://chargify.com/blog/dropping-sslv3/). A list of the likely breaking changes that might affect you are listed here: [Latest Breaking Changes](http://chargify.codeplex.com/wikipage?title=Latest%20Breaking%20Changes&referringTitle=Home). Also, if you're still having trouble - make sure you're specifically setting `ChargifyConnect.ProtocolType` to `SecurityProtocolType.Tls | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls12` (if possible, to handle fall back to lower TLS). If using .NET 4 or under, just set it to `SecurityProtocolType.Tls`.
Expand Down

0 comments on commit 26ef266

Please sign in to comment.