IPAddressRange 3.2.1
This library allows you to parse range of IP address string such as "192.168.0.0/24" and "192.168.0.0/255.255.255.0" and "192.168.0.0-192.168.0.255", and can conatins check. This library supports both IPv4 and IPv6.
Showing the top 20 packages that depend on IPAddressRange.
| Packages | Downloads |
|---|---|
|
Ocelot
Ocelot is an API gateway based on .NET stack.
|
1 |
|
Ocelot
Ocelot is an API gateway based on .NET stack.
|
3 |
|
Ocelot
Ocelot is an API gateway based on .NET stack.
|
5 |
|
Ocelot
Ocelot is an API gateway based on .NET stack.
|
7 |
|
Ocelot
Ocelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
|
3 |
|
Ocelot
Ocelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
|
4 |
|
Ocelot
Ocelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
|
5 |
|
Ocelot
Ocelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
|
6 |
|
Ocelot
Ocelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
|
8 |
|
Ocelot
Ocelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
|
11 |
v.3.2.1
- Fix implementation problem (Remove useless GetAddressBytes)
v.3.2.0
- Fix: Bits.GE/LE operations are reversed.(use GtE/LtE instead.)
- Improve: Bts.GtE/LtE methods are more faster now.
v.3.1.1 - Fix: Error if parsing IP address includes some spaces.
v.3.1.0 - Support parsing for IPv4 mapped to IPv6 address range.
v.3.0.0 - Sign the assembly. (make it to strong-named assembly.)
v.2.2.0 - Enhance: IPv4 shortcut notation support (like "192.168.0.0-255").
v.2.1.1 - Fix: Error if parsing IP address with scope id in the end.
v.2.1.0 - Enhance: Add "IsEqual" and "Decrement" methods to "Bits" utility class.
v.2.0.0 - [BREAKING CHANGE] Truncate .NET 4.0 support.
- Enhance: can serialize/deserialize json text by JSON.NET
v.1.6.2 - Support: .NET Standard 1.4 (.NET Core) and UWP
v.1.6.1 - Fix: Add some parameter checks for throwing ArgumentNullException
v.1.6.0 - Enhance: Add "ToCidrString()" and "GetprefixLength()" method.
v.1.5.0 - Enhance: Add constructors variation / Save memory usage.
v.1.4.0 - Enhance: Add IEnumerable<IPAddress> support.
v.1.3.0 - Enhance: support both "hyphen (-)" (0x002D) and "dash (–)" (0x2013) at begin-end format.
v.1.2.1 - Fix: "Parse()" and "TryParse()" methods throw IndexOutOfRangeException when bit mask length is invalid at CIDR format.
v.1.2.0 - Enhance: Add "Parse()" and "TryParse()" methods. (Instead, the constructor which has one string argument is obsoleted.)
v.1.1.0 - Enhance: Add "Contains()" method overload version of IPAddressRange argument.
v.1.0.6 - Fix Package: Repackage with Release build. (1.0.5 was Debug build)
v.1.0.5 - Fix: IPv4 CIDR range ".../32" causes crush.
v.1.0.4 - Enhance: support bit mask range not only CIDR range.
v.1.0.3 - Fix: Can not parse the address which contains hex string.
.NET Framework 4.5
- No dependencies.
UAP 0.0
- No dependencies.
.NET Standard 1.4
- NETStandard.Library (>= 1.6.1)
| Version | Downloads | Last updated |
|---|---|---|
| 6.1.0 | 4 | 12/05/2024 |
| 6.0.0 | 15 | 05/13/2024 |
| 4.0.0 | 3 | 12/03/2024 |
| 3.2.2 | 3 | 12/03/2024 |
| 3.2.1 | 3 | 12/10/2024 |
| 3.2.0 | 3 | 12/02/2024 |
| 3.1.1 | 3 | 12/02/2024 |
| 3.1.0 | 3 | 12/16/2024 |
| 3.0.0.1 | 2 | 12/09/2024 |
| 3.0.0-beta | 5 | 12/09/2024 |
| 2.2.0 | 3 | 12/03/2024 |
| 2.1.1 | 3 | 12/12/2024 |
| 2.1.1-beta | 5 | 12/10/2024 |
| 2.1.0.1 | 3 | 12/02/2024 |
| 2.1.0-alpha | 5 | 12/08/2024 |
| 2.0.0.4 | 6 | 11/23/2024 |
| 2.0.0.3 | 3 | 12/11/2024 |
| 2.0.0.3-beta | 2 | 12/12/2024 |
| 2.0.0-beta | 3 | 12/03/2024 |
| 1.6.2.7 | 2 | 12/04/2024 |
| 1.6.2.6-beta | 0 | 03/01/2017 |
| 1.6.2.1-beta | 5 | 12/04/2024 |
| 1.6.1 | 3 | 12/03/2024 |
| 1.6.0 | 3 | 12/04/2024 |
| 1.5.0 | 3 | 11/28/2024 |
| 1.4.0.1 | 3 | 12/03/2024 |
| 1.4.0 | 3 | 12/12/2024 |
| 1.3.0.1 | 2 | 12/04/2024 |
| 1.3.0 | 0 | 04/01/2015 |
| 1.2.1 | 3 | 12/04/2024 |
| 1.2.0 | 3 | 12/02/2024 |
| 1.1.0-beta | 3 | 12/12/2024 |
| 1.0.6 | 3 | 12/04/2024 |
| 1.0.5 | 3 | 12/13/2024 |
| 1.0.4 | 5 | 12/10/2024 |
| 1.0.3 | 3 | 12/02/2024 |
| 1.0.2 | 3 | 12/04/2024 |
| 1.0.1 | 5 | 12/09/2024 |
| 1.0.0 | 1 | 12/08/2024 |