Bug - Fixed Changes to URL handling in KoL broke KoLmafia

Opassa

New member
Kingdom of Loathing just underwent a silent update, it now loads a bunch of stuff from the subdomain images.kingdomofloathing.com instead of kingdomofloathing.com. Somehow KoLmafia needs to track these requests and which domain they're going to and rewrite them to go through KoLmafia instead of rewriting them to https://images/. Hopefully it's simple to fix, but I have no idea how to handle that. Maybe by rewriting the URL to include http://127.0.0.1:60080/images/*.php or something like that? I know some stuff comes from cloudflare and it seems to relay those requests just fine, so there must be some mechanism that can handle different domains.
 
The problem cascades from there (AFAIK it's not just images but also css and javascript? so not having it removes/breaks a lot of native functionality), and doesn't seem to be limited to relay browser. Most of my "start of day" scripts ran, but then I got exceptions from buying or eating karma shawarma, for example - still in gCLI.
 
There's ... a lot of things that aren't working for me right now. Combat action bar is completely non-functional, and while I can run combats with "adv" in the CLI, if I use "adv1" or if it's a combat started from an item, mafia doesn't register that a combat has started. At least until I load the page in relay browser. Don't know where to begin looking for what causes *that*.
 
People in my clan are saying r29223 fixed things.
People in the Games and Newbie channels say it fixed most of it, but there's still reports of lag for things like inventory. But that seems to be inconsistent. 3 seconds, 5 seconds, 15-45 seconds, 1 minute are all times I've seen reported before tonight's rollover.
 
My inventory took very long time to finish loading the first time (but I also cleared my mafia cache yesterday), but not the second time (all images cached in browser). Next check is ... I don't know when, I can't tell how long the browser caches them.
Next suspect would be the change from http to https, SSL adds some processing on its own and who knows what the protocol changes can cause.
Another suspect is browser addons, especially adblockers (I have ublock origin/umatrix/privacy badger) - AFAIK and IIUIC on firefox they hook into the request in such way that it serializes them (the images come in one after another instead of in batches). It is possible that the issue already existed for this reason, but we are noticing it because there was a bigger change.
 
Back
Top