I get a redirect from user_engine when using
curl -i -X POST -d "<xml_data></xml_data>"
http://<webpage>?_session_id=ABC
If I use
curl http://<webpage>?_session_id=ABC
the GET works fine.If it was a routing issue, I would
expect the GET not to work.I also removed the -i, but no difference.
I''m using
if request.post?
---
end
if request.get?
---
end
in the controller, request.get? works fine, so I don''t think
it''s a
controller problem, it''s not getting to the request.post?.
In the development.log file, when I do the GET, the session id
displayed is the same as the param value
Session ID: ABC
Parameters: {"_session_id"=>"ABC",
"action"=>..
but in the POST I see they are different:
Session ID: DEF
Parameters: {"_session_id"=>"ABC",
"action"=>...
Where the session id DEF is different from the session that had worked
previously (ABC).
Why is user engine generating a new session for POST? How is
user_engine making the determination that a new session id is needed?
As a result of the new session id, user engine thinks I''m a guest.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk
-~----------~----~----~----~------~----~------~--~---
