struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Don Brown (JIRA)" <j...@apache.org>
Subject [jira] Updated: (WW-2358) RestWorkflowInterceptor in struts2-rest-plugin is returning a status which kills browser sessions
Date Sat, 14 Jun 2008 04:31:05 GMT

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

Don Brown updated WW-2358:
--------------------------

    Component/s:     (was: Other)
                 Plugin - REST

> RestWorkflowInterceptor in struts2-rest-plugin is returning a status which kills browser
sessions
> -------------------------------------------------------------------------------------------------
>
>                 Key: WW-2358
>                 URL: https://issues.apache.org/struts/browse/WW-2358
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Plugin - REST
>    Affects Versions: 2.1.1
>         Environment: Struts 2.1.1-SNAPSHOT on Jetty 6.1.6
>            Reporter: Sarat Pediredla
>             Fix For: 2.1.3
>
>         Attachments: WW-2358.patch
>
>
> The RestWorkflowInterceptor in the struts2-rest-plugin is a cool addition but unfortunately
returns SC_BAD_REQUEST on validation fail, which might work with testing frameworks but kills
real browsers.
> The response tested on Safari 3 and Firefox 2.0.0.11 just shows a blank screen. 
> If I change the following line from,
> HttpHeaders info = new DefaultHttpHeaders()
>             	    .disableCaching()
>             	    .renderResult(method)
>             	    .withStatus(SC_BAD_REQUEST);
>             	
> to,
> HttpHeaders info = new DefaultHttpHeaders()
>             	    .disableCaching()
>             	    .renderResult(method);
> then it works great as the server returns the right result as of validation failure (editNew
in this case)
> I am not entirely sure what the solution to this would be; either using a status code
that the browsers will respond to or maybe not have a status code at all (although this might
not be strictly RESTful) given that errors are sent back in a Map.

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


Mime
View raw message