Re: LWP::ConsoleLogger::Easy messes the console on (seemingly) unicode LWP response: is it a case of broken unicode?

For any text in headers, you are best of with sticking to ISO-8859-1. For content, you have to mark that as UTF-8. Most likely, you want:

Content-Type: application/json; charset=utf-8

Depending on the content type, that charset may or may not also be marked within the content by the unicode mark at the beginning of the "file".

If the charset is not specified, most useragents will assume ISO-8859-1, according to HTTP spec. But some may infer other charsets, depending on things like the language header. Important here to note is that, while your request can specify any header you like, the server isn't really obligated to adhere to most of them. And the client will usually ignore all the headers you sent to the server and will only work on the headers that the server has sent back to you in the response.

For example, you set a 'Content-Type' request header. This is NOT a valid header. (Well, technically, it is valid HTTP, but it is ignored by servers because it's not in the spec as a client request header). The Content-Type header is a response header only, unless i seriously misremember the RFCs. The content type is set by the server and there is no in-header way to specify the charset the client wants.

For JSON, your best bet would probably to shove it through the JSON decoder library of your choice, hope it gets decoded correctly and then put it into your logger.

I haven't player with LWP::ConsoleLogger::*, but best bet is that it gets confused by a missing charset=utf-8 declaration or something. Most JSON modules on CPAN on the other hand make the mostly sensible choice of assuming that everything is UTF-8, because that's the same assumption JavaScript in most modern browsers would also make.

PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP

Comment on Re: LWP::ConsoleLogger::Easy messes the console on (seemingly) unicode LWP response: is it a case of broken unicode? Select or Download Code

Replies are listed 'Best First'.
Re^2: LWP::ConsoleLogger::Easy messes the console on (seemingly) unicode LWP response: is it a case of broken unicode? by Corion (Patriarch) on Aug 24, 2023 at 15:08 UTC
I think it's worse resp. even bug-report worthy. LWP::ConsoleLogger does not care about the encoding and blindly passes everything through to Text::SimpleTable::AutoWidth, which also doesn't care/handle encoding of stuff.	[reply]
Re^2: LWP::ConsoleLogger::Easy messes the console on (seemingly) unicode LWP response: is it a case of broken unicode? by bliako (Abbot) on Aug 24, 2023 at 21:27 UTC
`For example, you set a 'Content-Type' request header. This is NOT a valid header.` I was throwing at it all I could find JSON::XS did not have any problem `decode_json`'ing that JSON. And if I don't import and use the Logger `print $response->decoded_content;` works just fine (without binmode'ing STDOUT). Additionally, sometimes it fails (=messing the console) while printing `Content` and sometimes when it prints `Text` (which I believe is printing decoded JSON) I will follow what Corion said and report it. Though I hate dumping encoding bugs on unsuspected passerbys. thanks!	[reply] [d/l] [select]
Re^3: LWP::ConsoleLogger::Easy messes the console on (seemingly) unicode LWP response: is it a case of broken unicode? by cavac (Prior) on Aug 25, 2023 at 06:45 UTC
Though I hate dumping encoding bugs on unsuspected passerbys. Wish i had the same luxury. It feels like i'm spending half my life fixing encoding bugs these days. Unicode is great... when it works. Just last month i spend half an afternoon trying to fix a printing bug, until i realized that font i was using had a bug... But look at it this way: Humans have lots of different cultures and writing systems. The more Unicode bugs we fix, the more inclusive our programs become. In the long term, tearing down the walls that divide cultures will (hopefully) bring people closer together and reduce the prevalence of bigotry and wars. PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP	[reply]
Re^3: LWP::ConsoleLogger::Easy messes the console on (seemingly) unicode LWP response: is it a case of broken unicode? by NERDVANA (Priest) on Aug 25, 2023 at 21:12 UTC
I could be wrong, but I think the only thing that would corrupt a terminal would be control codes, and specifically the escape character \e. Any utility meant to dump protocol traffic to a terminal should always escape the control codes. Before reporting it, see if you can find the line that does the printing, and add this: `$str =~ /([\0-\x09\x0B\x1F])/sprintf("\\x%02X", ord $1)/ge;` [download] and see if it stops corrupting your terminal. Then you could submit a pull request instead of a bug report :-)	[reply] [d/l]