Skip to content
Inskey edited this page Dec 21, 2015 · 4 revisions
  1. To provide a flexible, close-to-the-core yet powerful API for dynamic content generation
  • Manipulation of all aspects of the HTTP Response packet
  • Build web pages in an object-oriented style by treating tags as objects and reusing components/code
  • Powerful tools for generating content at a high level
  1. To allow for customization at all levels
  • Change automatic response pages (e.g. 404) to your liking, even making them dynamic
  • Choose to load files into memory or have them streamed from the filesystem on request
  • See detailed information and have access to powerful commands in the console
  1. To have security from the ground up, eliminating the need for a conglomeration of add-ons and workarounds
  • Resistant to Slowloris, Tor's Hammer, and other attacks (fully configurable)
  • Built-in optional HTTP Tarpit - slows down vulnerability scans or makes them inaccurate
  • All code is in C# rather than an interpreted language such as PhP

A note on security: While NetDotNet is designed to resist attacks and scans, it is still the developer's responsibility to build secure web pages and reliable code.

Clone this wiki locally