Application Errors don't return right away.
When I handle errors in global.asax using Application_Error in my MVC3 app the web server does not end the respone for over a minute and the browser just hangs. Application_Error is firing and I'm logging the message and that happens right away. The only fix seems to be to turn On customerrors in the Web.Config which seems to bypass Application_Error.
I've ripped out Elmah and Log4Net just in case.
I haven't tried ripping out DotNetOpenAuth yet. (mostly because it's required) Wouldn't be surprised if that was it.
I've tried about 40 different settings and am out of ideas.
You can recreate by going to:
http://nodeler.com/login
Use firebug in Firefox to mess with the antiforgerytoken and then login with any bogus data. That should trigger an error.
Christopher
Discussions are closed to public comments.
If you need help with AppHarbor please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by rune on 12 Apr, 2011 05:18 PM
Hi Christopher,
I was able to reproduce the issue as you described. We haven't experienced the same issue ourselves and I'm actually quite certain it's something DotNetOpenAuth does - I've previously seen people having issues with long running requests in that too. If you figure out what it is please let us know!
Thanks,
Rune
rune closed this discussion on 12 Apr, 2011 05:18 PM.
cdeutsch re-opened this discussion on 13 Apr, 2011 11:55 PM
2 Posted by cdeutsch on 13 Apr, 2011 11:55 PM
Thanks for your help.
I ripped pretty much every module out and it was still happening.
Calling Server.ClearError() in the Application_Error handler in Global.asax
seems to solve the issue. I'm not sure what other hook is trying to process
that error after Global.asax but it doesn't happen locally.
Just letting you know. I'm good for now. ;)
Christopher
On Tue, Apr 12, 2011 at 12:18 PM, Rune Sørensen <
[email blocked]> wrote:
Support Staff 3 Posted by rune on 14 Apr, 2011 06:58 AM
Hi again,
Just wanted to let you know that we've been able to reproduce the issue and it seems like it's a problem on our end. I'll let you know as soon as it's been fixed!
Thanks a lot for reporting this.
Best,
Rune
Support Staff 4 Posted by friism on 25 Apr, 2011 10:49 PM
We have now resolved this issue, thanks for reporting.
friism closed this discussion on 25 Apr, 2011 10:49 PM.