0

I'm trying to enable a Glimpse icon on all the error pages to see what happened behind the scenes where debugging and tracing is most important, and I cannot make Glimpse work.

What I've tried:

<glimpse defaultRuntimePolicy="On" endpointBaseUri="~/Glimpse.axd">
    <runtimePolicies>
      <statusCodes>
        <add statusCode="500"/>
        <add statusCode="404"/>
      </statusCodes>
    </runtimePolicies>
</glimpse>

Does not help - no Glimpse icon in the corner of error pages. On "200 OK" pages Glimpse works fine.

I'm wondering if I'm the only one who thinks that tracing of request handling in case of exception is A MUST and #1 scenario that tools like Glimpse should cover?

Philipp Munin
  • 5,610
  • 7
  • 37
  • 60
  • Do you want the user/client to see the icon in their browsers? – pollirrata Jun 05 '13 at 22:32
  • Yes. I want to see Glimpse Icon on error pages as always as I see it on success 200-code pages. I would say seeing it on error page is more important then seeing it on success pages. I actually think it's obvious. – Philipp Munin Jun 05 '13 at 22:39
  • Are you using custom error pages or regular .Net yellow page messages? Are you running in Integrated pipeline mode? – Jon Adams Jun 13 '14 at 23:31
  • I use standard .NET error yellow page, that was a while ago, it probably was integrated mode – Philipp Munin Jun 15 '14 at 00:53
  • I recently tried this and could not get glimpse to show up on YSOD error pages. – ctorx Nov 11 '14 at 22:52

0 Answers0