Skip to content

fix: remove incorrect Content-Encoding: UTF-8 header from ticket username endpoint - #716

Merged
ymarcon merged 1 commit into
masterfrom
fix/715
Aug 24, 2026
Merged

fix: remove incorrect Content-Encoding: UTF-8 header from ticket username endpoint#716
ymarcon merged 1 commit into
masterfrom
fix/715

Conversation

@ymarcon

@ymarcon ymarcon commented Aug 24, 2026

Copy link
Copy Markdown
Member

ResponseBuilder.encoding("UTF-8") sets the Content-Encoding header, which is meant for transfer encodings like gzip, not charsets. Apache HttpClient 5 rejects it as invalid, breaking Mica SSO ticket validation. The charset is already correctly declared via @produces text/plain;charset=utf-8.

Fixes #715

…name endpoint

ResponseBuilder.encoding("UTF-8") sets the Content-Encoding header, which is
meant for transfer encodings like gzip, not charsets. Apache HttpClient 5
rejects it as invalid, breaking Mica SSO ticket validation. The charset is
already correctly declared via @produces text/plain;charset=utf-8.

Fixes #715
@ymarcon
ymarcon requested a review from kazoompa August 24, 2026 10:54
@ymarcon
ymarcon merged commit 3b88566 into master Aug 24, 2026
2 checks passed
@ymarcon
ymarcon deleted the fix/715 branch August 24, 2026 10:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

TicketResource.getUsername() incorrectly sets Content-Encoding: UTF-8, breaking ticket authentication with Apache HttpClient 5

1 participant