Page MenuHomePhabricator

wm-bot doesn't set charset=utf-8, which breaks (amongst other things) emoji rendering
Closed, ResolvedPublic



In Chrome stable, the emoji render for me as incorrect characters, rather than a single codepoint:

[18:04:59] <cdanis>	 🥸

Sending response header content-type: text/plain; charset=utf-8 instead of the content-type: text/plain we currently send would probably fix this.

Event Timeline

fgiunchedi triaged this task as Medium priority.Apr 14 2020, 9:31 AM

@RLazarus encountered this today while doing some retrospective on Datacenter-Switchover.

@bd808 do you know who runs/owns wm-bot?

@bd808 do you know who runs/owns wm-bot?

I would consider @Petrb to be the primary "owner" of wm-bot, but there are other folks who work on it as well. Some of them are listed at

jbond claimed this task.
jbond subscribed.

@CDanis i went to look at this but it seems like it may be fixed. checking the URL in chrome and FF seems to render correctly. further i notice we are getting the suggested header now

$ curl --head                                    
HTTP/2 200 
server: nginx/1.18.0
date: Tue, 23 May 2023 13:21:34 GMT
content-type: text/plain; charset=utf-8
content-length: 9336
last-modified: Mon, 13 Apr 2020 23:06:22 GMT
etag: "2478-5a33421af7ada"
accept-ranges: bytes
vary: Accept-Encoding
strict-transport-security: max-age=31622400
x-clacks-overhead: GNU Terry Pratchett

going to tentatively close but please reopen if i missed something