Closed chenkins closed 1 month ago
@JaniruTEC any particular reason for this change?
we shouldn't set such a header globally in application.properties
, though. Just for specific resources.
I know, but still I wonder why we're defaulting to text/html
.
2111e99 needs to be considered in the context of its PR (#250) and the next commit after (289014b). It was created for the purpose of enabling that next commit. The content type was already defined at that point in time, tho: https://github.com/cryptomator/hub/commit/2111e9904afdafc639daae6b347be97c4073c006#diff-2379b203b20f6c78d9aaf2d7437eaff6d257e2c82136a2c31e770e975afd1bf2R291
fyi: I just retested with Quarkus 3.8.5: There is now just one Content-Type header field in the response (but sadly not the one specified by the annotation).
Please agree to the following
Summary
Duplicate Content-Header for GET /api/vaults/{vaultId}/access-token
System Setup
Steps to Reproduce
Expected Behavior
One Content-Type header field
Actual Behavior
Two Content-Type header field, I suppose one from
appliation.properties
and one from
@Produces(MediaType.TEXT_PLAIN)
Reproducibility
Always
Relevant Log Output
Anything else?
Introduced in https://github.com/cryptomator/hub/commit/2111e9904afdafc639daae6b347be97c4073c006
patch: