[ 
https://issues.apache.org/jira/browse/OLIO-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682110#action_12682110
 ] 

William Sobel commented on OLIO-62:
-----------------------------------

This is a bug in the 2.0.1 version of the HTTP client. The event and person are 
added and then the application redirects to the show page. The redirect is 
interpreted as a POST again by the http client and it tries to post to a show 
url. This is a error and does not follow the HTTP specification. 

The manual redirect is required, but it can be solved with a manual redirect. 
There will be a info message coming out about not following redirects. This is 
also stupid.

> Rails Driver does not check the responseBody of doAddPerson or doAddEvent 
> POSTs for flash messages indicating an error occured
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: OLIO-62
>                 URL: https://issues.apache.org/jira/browse/OLIO-62
>             Project: Olio
>          Issue Type: Bug
>          Components: rails-driver
>         Environment: Any
>            Reporter: Mandy Waite
>            Assignee: William Sobel
>
> When running into a problem with MySQL and duplicate keys which for most of a 
> run resulted in no users or events being inserted into the database. It was 
> seen that this kind of failure was not picked up by the Rails Driver and 
> therefore doAddPerson and doAddEvents oeprations were flagged as being 
> successful regardless of  whether inserts were made or not.
> The symptom to look for is that if the add fails, the status returned by the 
> HTTP POST is SC_OK and not SC_MOVED_TEMPORARILY (i.e.: a redirect) and a 
> flash message is added to the page, either: "Could not create event" for 
> failing to add an event, or "Failed to create user" for  failing to add a 
> user.

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

Reply via email to