Public bug reported:
Sending list settings to the REST server (PATCH /lists/[fqdn_listname]/config) raised the following HTTPError:
HTTPError: HTTP Error 400: Unexpected parameters: bounces_address, created_at, digest_last_sent_at, fqdn_listname, host_name, http_etag, join_address, last_post_at, leave_address, list_id, list_name, next_digest_number, no_reply_address, owner_address, post_id, posting_address, request_address, scheme, volume, web_host
The HTTPError is thrown because these paramaters are not listed in ATTRIBUTES (src/mailman/rest/configuration.py:159). However all of these parameters were received via GET /lists/[fqdn_listsname]/config.
Are the parameters simply missing in the ATTRIBUTES dict or is there any other reason they're not accepted?
** Affects: mailman Importance: Undecided Status: New
** Tags: mailman3 rest
Are you sure you have an up-to-date configuration.py file? All those parameters are named in ATTRIBUTES except http_etag, which is an artifact of the GET. If you remove http_etag from the PATCH call, does it work for you?
If that's the only offender then there might be a bug in the error message, since it should only complain about http_etag in the PATCH.
Can you post some Python to reproduce the problem?
** Changed in: mailman Status: New => Incomplete
What's the most decent way to take back a bug report? :-/
Trying to reproduce it again I found out the reason for the bug was just me messing up a test case. Sorry...
** Changed in: mailman Status: Incomplete => Invalid
-
Barry Warsaw -
Florian Fuchs