The default trace writers do not currently special-case HttpResponseException, and therefore trace at TraceLevel.Error. This is confusing, because it means simple user error in the URI will generate an error trace. This makes it hard to use the tracing layer to report errors. The System.Diagnostic, ETW, and Memory trace writers all try to correct for this to convert it back into a warning.
Recommend the default tracing logic should trace at TraceLevel.Warn whenever the exception is HttpResponseException.
Comments: I opened isssue https://aspnetwebstack.codeplex.com/workitem/1201 with the recommendation to fix this for "all" scenarios simply by moving the code from SystemDiagnosticsTraceWriter to ITraceWriterExtensions.
Recommend the default tracing logic should trace at TraceLevel.Warn whenever the exception is HttpResponseException.
Comments: I opened isssue https://aspnetwebstack.codeplex.com/workitem/1201 with the recommendation to fix this for "all" scenarios simply by moving the code from SystemDiagnosticsTraceWriter to ITraceWriterExtensions.