1. URL is resolved and matched against content in the wwwroot and subdirectories. If its extension is .html, it is treated as an IW Page. If not, processing is stopped and the file is served as static content.
  2. A default template is searched for if one is not specified in the .cfg file.
  3. The IWP and Template files are merged.
  4. If the Template file is cascading, the templates are merged until no more cascading parents are found.
  5. HTTP and Cookie tags are processed seperately. This allows these tags to be embedded inside attributes of other tags, allowing user data to affect other tag functionality.
  6. Remaining tags are processed.
  7. Resulting HTML is sent to the browser.