@JagexAllstar I noticed there's totally broken HTML on news pages (or just the Giants' Foundry one?). This one broken tag causes 49 different errors in the w3 html validator, the particular HTML parser I was using, entirely fails on it as invalid.
@JagexAllstar hey, you mentioned a GIM hiscores API potentially coming out in October, is it out yet? Or if not, any update on it? just checking, thank you!
@JagexAllstar Hey! Can you provide any help/info on the hiscores API for group ironman to help me get started in adding support for it to my nodejs library? Just a couple URL examples maybe? the new UI looks great btw๐
@JagexAllstar Was something called "Incapsula" recently installed on the RS website servers? Suddenly today/recently im getting errors for requests that worked fine for years, due to non-spec headers that Incapsula is apparently adding?
@JagexAllstar can parse the malformed header if you use `--insecure-http-parser` flag...which isnt ideal at all. Heres a github issue with more info if it helps (tldr: sending non-spec/malformed headers breaks stuff, as you'd expect): https://t.co/CEB2S7JLmF
@JagexAllstar and I have no idea how incapsula works, but just to share the info, the github issue i saw says you can ask incapsula support to remove this header. id assume reasonably you could just remove it yourself though without their input
@JagexAllstar Cool - if it helps ive heard that these things are apparently true: 1. incapsula is known to cause issues like this (seen github issues, even unrelated to nodejs) 2. they insert a random CLRF in the middle of a Set-Cookie header value. - which is probably the cause (1/2)
@JagexAllstar with curl/wget/browser it works fine, fails in nodejs. Heres my URL/test code: ```require('node-fetch')('https://t.co/yb0qEK5ddW')``` Maybe try running it if you have it installed. I guess its because of the parser used by nodejs is "strict" or "different"