WoWCenter.pl
wikass zabił Mythrax the Unraveler (Normal Uldir) po raz 2.     
kuturin zdobył 7th Legionnaire's Cuffs.     
Nikandra spełnił kryterium Loot 200,000 gold osiągnięcia Got My Mind On My Money.     
Tooly zdobył Fairweather Helm.     
Muattin zdobył osiągnięcie The Dirty Five.     
Yoozku zdobył Parrotfeather Cloak.     
Mlody89 zdobył Royal Apothecary Drape.     
Weakness zabił Dazar, The First King (Mythic King's Rest) po raz 6.     
liq spełnił kryterium osiągnięcia Saving for a Rainy Day.     
Osiol spełnił kryterium osiągnięcia Saving for a Rainy Day.     
Wuntu zabił Zek'voz, Herald of N'zoth (Heroic Uldir) po raz 1.     
Olsa zabił Vectis (Heroic Uldir) po raz 6.     
Sarenus spełnił kryterium osiągnięcia Saving for a Rainy Day.     
kajtasus zdobył osiągnięcie Come Sail Away.     
ossir spełnił kryterium osiągnięcia Saving for a Rainy Day.     
mcpablo spełnił kryterium Alliance players slain. osiągnięcia Frontline Slayer.     
Emmm zabił Taloc (Heroic Uldir) po raz 17.     
AsaGorth spełnił kryterium Big-Mouth Clam osiągnięcia The Oceanographer.     

[BUG] Realm Status API

blizz -> wysłany:
What a journey to get this bug to the right people. I am originally a EU player and found a bug while making Java wrapper library for the new API (btw kudos on that, love the new API). Posted on the EU forums ( http://eu.battle.net/wow/en/forum/topic/2123512342 ) to no avail. Mailed to the people of the US support team who misunderstood me and were so kind as to redirect me to specific US forums to post in... In a last attempt, I bought a US license and leveled a char so I could post on these forums. Hard work to get a bug where it’s supposed to go, but got there in the end! :) /cheer

Now for the bug. When checking the headers for the new Realm status API I noticed that the Content-Type header has the correct MIME-type but the wrong character encoding.

The Content-Type header has the value of application/json;charset=ISO-8859-1. As you can see the character encoding is set to ISO-8859-1 (Latin-1). The content itself is UTF-8. This is of course a good thing, we want the content to be UTF-8 encoded. But the charset in the Content-Type header needs to be set accordingly.

This might not have been apparent at first because the lower range characters of the ISO-8859-1 set are equal to the lower range characters in UTF-8. However, it becomes plainly apparent with higher range characters (e.g. Cyrillic characters ).

If you were to go to the European realm status ( http://eu.battle.net/api/wow/realm/status ) and try to view it in a browser like Chrome, you would see that the server names in Cyrillic look like gibberish. This is because the browser tries to render the characters in the character set found in the Contet-Type header (i.e. ISO-8859-1).

So, to make a long story short. Can the value for charset in the Content-Type header be set to UTF-8?
blizz -> wysłany:
First of all, thanks for going the extra mile to report this.

I've identified the issue and this will be resolved with an update later today.