Re: Programmatically turn off custom errors for current request
From: Scott Allen (bitmask_at_[nospam)
Date: 06/30/04
- Next message: John: "listbox and sql stored procedure"
- Previous message: RLoski: "Re: Visual Studio 2003 hangs"
- In reply to: Matt: "Programmatically turn off custom errors for current request"
- Next in thread: Matt Caton: "Re: Programmatically turn off custom errors for current request"
- Reply: Matt Caton: "Re: Programmatically turn off custom errors for current request"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 30 Jun 2004 11:25:54 -0400
Hi Matt:
Since no one has responded as yet I though I'd through out an idea I
had.
If you handle the Application_Error event in global.asax you might be
able to prevent the redirect with a call to ClearError. I have not
tried this, mind you, just an idea.
If you need to get "state" information from AuthenticateRequest to
Application_Error, you could use the Content.Items collection to hold
some sort of sentinal object.
HTH,
-- Scott http://www.OdeToCode.com On 30 Jun 2004 05:36:11 -0700, Matt.Caton@BTInternet.com (Matt) wrote: >Hello all, > >The app we are working on uses custom errors extensively to provide >friendly error pages to users whilst logging the actual exceptions >behind the scenes. > >However.... We are now having to integrate some Web services into the >application using the existing architecture. These Web services are >secured using Forms Authentication. Hence, we need to turn the default >behavior of Forms Authentication (redirects to login pages, etc) into >exceptions that can be handled by a non GUI client (ie. Web service >consumer). > >Heres the problem.... > >In the AuthenticateRequest event, we check if a secure Web service is >being called. If so, we check for an authentication ticket in the Soap >header. If its not there, we throw a "MissingAuthenticationTicket" >custom exception. This gets wrapped in a SoapException and we want >this to get passed to the client. > >However.... the custom error page gets called instead, redirecting the >client to Error.aspx and logging the exception on the server. This is >secure, but very hard to handle at the client. > >Anyway, what I would like to be able to do is just before throwing the >MissingAuthenticationTicket exception, turn off custom errors for this >request only. Hence the exception would get passed to the client as >expected. > >Is there anyway to achieve this? > >Thanks in advance for any help, >Regards, >Matt
- Next message: John: "listbox and sql stored procedure"
- Previous message: RLoski: "Re: Visual Studio 2003 hangs"
- In reply to: Matt: "Programmatically turn off custom errors for current request"
- Next in thread: Matt Caton: "Re: Programmatically turn off custom errors for current request"
- Reply: Matt Caton: "Re: Programmatically turn off custom errors for current request"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|