[issue2551048] Config: secret_key in [web] section: Default not constant for multi-process
Ralf Schlatterbeck <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.devel |
|---|---|
| Message-ID | <[email protected]> |
New submission from Ralf Schlatterbeck: When running roundup as a multi-process application like CGI or WSGI, the default value for the variable 'secret_key' in secion [web] is not constant and will be different for each process. The reason is that it uses a random value for initialisation if the item is unconfigured. This random value is different in each process. The implication is that with the (empty) default value for secret_key REST-API updates will not work because the etag verification will fail (at least if the first request to retrieve the etag and the second request to do the update are serviced by different processes which is very likely). We should either come up with a fix or document this in the REST-API documentation. ---------- messages: 6558 nosy: rouilj, schlatterbeck severity: normal status: new title: Config: secret_key in [web] section: Default not constant for multi-process _________________________________________________ Roundup tracker <[email protected]> <https://issues.roundup-tracker.org/issue2551048> _________________________________________________