Rsft.HttpCookieSecure
Metadata
| Authors | Rolosoft |
|---|---|
| Copyrights | Copyright 2013 |
| Description | Encryption and decryption of HTTP cookies, provides protection against manual cookie tampering. |
| Language | en-US |
| LicenseUrl | http://www.apache.org/licenses/LICENSE-2.0 |
| Owners | Rolosoft |
| ProjectUrl | https://code.google.com/p/http-cookie-secure/ |
| ReleaseNotes | Initial release. |
| RequireLicenseAcceptance | False |
| Summary | IIS server side software for .NET framework 4.0. Provides encryption and decryption of HTTP cookies together with tamper protection. |
| Tags | rolosoft IIS cookie |
| Title | HttpCookieSecure |
| PackageSize | 17481 |
| PackageHashAlgorithm | SHA512 |
| PackageHash | AEzICzaRWae4SSS/xNrnHzc8XdxOuF6qHCFXQB4ub8a2+3M4QZTGM5XxnWgxy9xUIePr3aZHg+yuKPTULbD4iQ== |
| DownloadCount | 000000 |
| CreatedDate | 2013-04-09T13:36:02 |
Access
You can access data for this project using the tools and addresses described below.
NuGet (nuget.exe)
- Installing the package (HTTP Basic authentication):
-
nuget install Rsft.HttpCookieSecure -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
nuget install Rsft.HttpCookieSecure -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
NuGet (Package Manager Console)
- Installing the package (search all configured feeds):
-
Install-Package Rsft.HttpCookieSecure
- Installing the package (HTTP Basic authentication):
-
Install-Package Rsft.HttpCookieSecure -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
Install-Package Rsft.HttpCookieSecure -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
- Uinstalling the package:
-
Uninstall-Package Rsft.HttpCookieSecure
OpenWrap
- Installing the package:
-
o add-wrap Rsft.HttpCookieSecure
- Uninstalling the package:
-
o remove-wrap Rsft.HttpCookieSecure
Versions
A version is snapshot of a project's source code. It does not need to follow the Major.Minor.Revision.Build numbering pattern. It can be an arbitrary string of text that identifies a release or a build, in particular including meaningful words like beta, RC or RTM.