Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Mocca sends an invalid Content-Encoding (UTF-8) #63

Open
crankydillo opened this issue Feb 17, 2022 · 1 comment
Open

Mocca sends an invalid Content-Encoding (UTF-8) #63

crankydillo opened this issue Feb 17, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@crankydillo
Copy link
Contributor

I have seen this happen for the JAX-RS client.

This is almost certainly an issue with the underlying HTTP library. Based on what I see it would be surprising if it didn't affect all the supported clients, but maybe that's not true. I'd think the server we use in functional tests would catch a problem in that area. Regardless, I'll see if I can quickly submit a reproducer.

Even though the fix is likely in HTTP lib, I'm filing here to track for our project.
@crankydillo crankydillo added the bug Something isn't working label Feb 17, 2022
crankydillo pushed a commit to crankydillo/mocca that referenced this issue Feb 17, 2022
Test that shows Content-Encoding issue with JAX-RS client paypal#63
eb8905d 
Fix should be done in feign.

 paypal#63
crankydillo pushed a commit to crankydillo/mocca that referenced this issue Feb 17, 2022
Test that shows Content-Encoding issue with JAX-RS client paypal#63
6829aef 
Fix should be done in feign.

 paypal#63
@crankydillo crankydillo mentioned this issue Feb 17, 2022
Closed
@fabiocarvalho777 fabiocarvalho777 added this to the 0.0.7 milestone Feb 17, 2022
@crankydillo
Copy link
Contributor Author

A potential work-around is to register some kind of filter that will manipulate the headers created by the underlying HTTP lib. I think JAX-RS impls typically have that flexibility. Didn't test this theory at all though.

@fabiocarvalho777 fabiocarvalho777 removed this from the 0.0.7 milestone May 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@crankydillo @fabiocarvalho777