Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

About

News Press Releases News Coverage Press KitCareersContact DNN

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Failed Request Tracing

Return to previous page

Edit
  • 4/7/2015
  • 1387 Views
Report

Comments

1387 Views

Failed Request Tracing

Last updated long time ago

Comments

Common

(Enter the content of this article below)

Advanced

 

Background

II7 introduced a new troubleshooting tool called Failed Request Tracing. This will provide detailed error messages as well as what may be causing a site to load slowly. This can be enabled on a site by site basis. It uses a simple wizard to create and edit the various rules but supports a lot of features to help in detecting site problems. Amongst it's capabilities are:

  • Monitor requests to any file type you specify, including .asp, .aspx and .php.
  • Check full request and response HTTP headers to make sure all required data is available.
  • Calculate how many bytes were sent back and forth, and how long it took to process the request in each pipeline step.
  • Filter on requests that take over N seconds to process.
  • Filter on certain HTTP response codes, such as 403, 404 or 500.
  • Filter on filenames with wildcards, such as "login*.aspx".
  • Know which HTTP modules were used to handle the request.
  • See how routing and URL rewriting affect request processing.
  • Monitor which application pools were used to handle the request.
  • See how load balancing (if enabled) is working and which server is responding to the request.
  • Select the appropriate providers for tracing events, such as web server caching, compression, ASP.NET infrastructure, and so on

References

Contents
No sections defined
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out