3

Resolved

Configurable elmah details path

description

I don't use the default elmah.axd to view my errors. Instead I use this https://github.com/alexanderbeletsky/elmah.mvc.controller

A web.config setting for configuring the path to the part before detail/?id=guid would be nice.

file attachments

comments

stevenlauwers22 wrote Nov 6, 2011 at 10:02 AM

Hi, thanks for logging this.

I wasn't aware of the existence of the Elmah MVC package, but frankly I don't really see how it adds value to what Elmah is today (maybe except for the security).
In my opinion something like Elmah should be as unobtrusive as possible. The Elmah MVC package requires you to add an area & controller and register a route.
Registering an HttpHandler for this seems like a much cleaner solution to me, even with an MVC application.

So, at the moment I'm not really planning to implement this, unless it gets more votes.

rbigbie wrote May 3, 2012 at 3:40 PM

I too also use a different location path for the elmah.axd. When I clikc on the View link inside Glimpse for Elmah I also get the strange detail/? URL served up. Am I missing something? Can't we configure where the elmah.axd location is for Glimpse to display the view details of an error? If we can't fix this, then I am going to abandon using Glimpse for Elmah.

stevenlauwers22 wrote May 10, 2012 at 11:36 AM

@rbigbie could you tell me more about the situation you're in? What's the exact URL that's being served up and what would you expect it to be?

Did you modify the path of the Elmah HTTP handler from elmah.axd to something else? Because those changes should be picked up by the plugin, modifications of any other form our not noticed by the plugin at the moment.

If you could tell me what you're exactly doing than maybe I can build in support for it.

Cheers

Markl_nz wrote May 15, 2012 at 12:36 AM

Steven, I'm also using the Elmah MVC package.

Consider that accessing error logs is an important administrative function for any web application. By having the standard .axd approach it means that this is accessed via a separate means to the rest of the administrative functionality exposed by the web application. It seems to me that the ADMIN area that the Elmah for MVC package creates is a perfectly reasonable approach to take, and it's disappointing that you seem uninterested in adding a simple configuration option to your add-in.

stevenlauwers22 wrote May 15, 2012 at 12:10 PM

@Markl_nz, I didn't say I wasn't interested to implement something to support a configurable details path. I merely asked for more input on how the users of the plugin have elmah set up so I can make a proper decision on what I'm going to do.

The primary purpose of Glimpse for Elmah is to integrate well with Glimpse & Elmah. Integrating it with Elmah.Mvc or ElmahR might require a different approach. Maybe a configuration settings works for Elmah.Mvc but not for ElmahR, so I need more details on how people are using the plugin before taking any action.

In the meanwhile, feel free to fork my code to add the configuration option for the details URL.

rbigbie wrote May 15, 2012 at 7:44 PM

@stevenlauwers22 Thank you for responding and taking interest in this problem. I have attached a screen shot with the mouse hovered over the link to the detail screen. You will see the resulting popup window from when I click on the link. I protect my ELMAH by using a different location on my site. I have attached the screen shot as a file to this reply.

I will also post my web.config related entries and the global.asax code related. Hope this answers your question. Thank you.

rbigbie wrote May 15, 2012 at 7:45 PM

Here is the web.config entries

rbigbie wrote May 15, 2012 at 7:46 PM

Here is the Global.asax code for the routes.