PUT to /settings/readonly does not set correct Content-Type

Description

When the user switches to and from the reader view the REST resource /settings/readonly is not correctly setting the Content-Type header of the response as text/plain, which then defaults to text/html by the means of JAX-RS defaults.

This can cause errors when used with active network components that rewrite HTTP headers or body. The REST operation should set the correct Content-Type. Some network setups seem to reencode the HTTP body and add the "missing" HTML basic mark-up, which will make the switching to and from the reader view impossible.

Environment

None

Assignee

Unassigned

Reporter

Sync User [K15t]

Participants

None

QA Status

None

Deployment

None

Documentation Status

None

UI Concept

None

External Votes

None

Components

Sprint

None

Fix versions

Affects versions

Configure