What steps will reproduce the problem?
1.
curl in a new session request
2.
curl in a publish request without setting the session-id
What is the expected output? What do you see instead?
With <allow_invalid_session_id allow="yes"/> in the config file I would expect
the above publish to be allowed, but an InvalidSessionId error is returned.
Original issue reported on code.google.com by smat...@gmail.com on 14 Jun 2012 at 1:10
Original issue reported on code.google.com by
smat...@gmail.com
on 14 Jun 2012 at 1:10