In response to MBS-6152, user collections can now be included thanks to the `user-collections` `inc=` parameter.

However, when requesting `user-collections` along with another user-related include (`user-tags` or `user-ratings`), the server responds with a `400 Bad Request`, even though the actual XML data follows.

For instance, compare the four following requests for a release which belongs to one of the authenticated user's private collections:

• http://musicbrainz.org/ws/2/release/a4326c18-4cf9-4e16-a289-2e6e7508d450?inc=collections yields `200 OK`, and returns only the public collections in which this release appears; this is the expected behaviour.
• http://musicbrainz.org/ws/2/release/a4326c18-4cf9-4e16-a289-2e6e7508d450?inc=user-collections yields `200 OK`, and returns the public collections in which this release appears, along with the user's private collection; this is the expected behaviour.
• http://musicbrainz.org/ws/2/release/a4326c18-4cf9-4e16-a289-2e6e7508d450?inc=user-tags+collections yields `200 OK`, and returns the public collections in which this release appears, along with the user's private collection; this is the expected behaviour (see [here](https://tickets.metabrainz.org/browse/PICARD-421?focusedCommentId=27521&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-27521)).
• http://musicbrainz.org/ws/2/release/a4326c18-4cf9-4e16-a289-2e6e7508d450?inc=user-tags+user-collections yields `400 Bad Request`, but still returns the public collections in which this release appears, along with the user's private collection; the XML is as expected, but *the status code is invalid*.

Using `user-ratings` instead of `user-tags` in the above requests gives the same results.