You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Matej Knopp (JIRA)" <ji...@apache.org> on 2007/08/26 22:07:30 UTC

[jira] Resolved: (WICKET-780) Internal server error 500 unresolvable in Ajax Debug Window

     [ https://issues.apache.org/jira/browse/WICKET-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Knopp resolved WICKET-780.
--------------------------------

    Resolution: Fixed

I modified the javascript to output error to ajax console. However, I'll not change it to display the page - there is ajax error handler you can configure in that case and this would break it.

> Internal server error 500 unresolvable in Ajax Debug Window
> -----------------------------------------------------------
>
>                 Key: WICKET-780
>                 URL: https://issues.apache.org/jira/browse/WICKET-780
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.2.6, 1.3.0-beta2
>            Reporter: Jim Hunziker
>            Priority: Minor
>             Fix For: 1.3.0-beta4
>
>         Attachments: fix.diff
>
>
> When an internal server error (code 500) occurs in the response to an ajax request, it's not possible to get the text of the error.  The Wicket Ajax Debug Window only says "ERROR: Received Ajax response with code: 500".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.