On 14 Apr 2011, at 8:04 PM, Andrew Colin Kissa wrote:
>> Thu Apr 14 13:00:19 2011 - routing 0 routes 0
>> [pid: 8559|app: 0|req: 3/5] 50.56.118.60 () {34 vars in 710 bytes} [Thu Apr
>> 14 13:00:19 2011] POST /messages/view/ACF272602A8.A7256/ => generated 1093
>> bytes in 2 msecs (HTTP/1.1 403) 3 headers in 148 bytes (0 async switches on
>> async core 0)
>>
>> 403 errors
>
> Exactly what i thought, will provide a fix tomorrow.
I have looked at this, unfortunately the changes with in Django total break the
distributed release mechanism
in Baruwa versions 1.0.x, There is no secure way to fix this in those versions
as each node generates its own
CSRF token and there is no way to synchronize this within the cluster at the
moment.
The work around would be to release from the actually node. Release 1.1.0 will
restore this functionality when
released.
--
Baruwa - www.baruwa.org
_______________________________________________
Baruwa mailing list
[email protected]
http://lists.baruwa.org/mailman/listinfo/baruwa
