-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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.
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
Readme downloaded with wrong encoding #920
Comments
@Bilge are you able to reproduce this bug if you make the request via CURL? And then would you mind pasting your findings? If you could paste your results using |
How could I possibly reproduce it using cURL given that this is a Ruby encoding error? |
@Bilge Sorry—our request was unclear. Seeing the verbose curl output is always our first step in troubleshooting these things, even if we suspect that the problem is in Ruby. We're seeing
Classifying this as a bug in the library, thanks for reporting it. |
@kytrinyx can you point me along the right direction in fixing this? Looks like all we need to do is check if the response has base64 inside the encoding then encode content as base64.
|
This looks like a different issue. Did you mean to solve this one? |
…ismatched encoding Fix broken encoding (fixes #920)
Downloading this readme results in a string with the wrong encoding (should be
UTF-8
).This problem manifests itself when trying to parse it with a markdown processor such as Kramdown.
The text was updated successfully, but these errors were encountered: