kick.com still producing 404 bad request error with hz+ active, after version update meant to fix this issue

[eitaniel]

ATTENTION! If you don't follow this template then your issue will be immediately closed.

Description of the problem

greetings

i'm writing to confirm that the fixes you stated you'd perform for hz+ on kick.com seem to not have been implemented. I am still getting 404 bad request error page upon activating hz+ and attempting to surf kick.com. it's almost instant fail.

did you implement the fixes you suggested would be done according to this issues thread? I've had the addon deactivated as recommended since early June, with the hope of it being fixed as stated in this thread with the next version update (1.0.207), so it's confusing why this seems not to be the case.

I raised this issue two months ago in this post: https://github.com/extesy/hoverzoom/issues/1156

Url of the page where the problem occurs (not the image url)

kick.com

Steps to reproduce the problem (include image url here)

1. activate hover zoom plus, with no site exceptions (ie. normal function to be active on all sites online)
2. visit kick.com, and start surfing normally, therein.
3. site will produce 404 bad request and eventually not load the site on refresh

OS version, extension version

windows 10 pro hz+ v. 1.0.207

[GrosPoulet]

@eitaniel i did not manage to reproduce the issue. Please remove & add back HZ+ then try again. BTW, i fixed a bug with clips (#1178), not related with the issue you reported.

[eitaniel]

@eitaniel i did not manage to reproduce the issue. Please remove & add back HZ+ then try again. BTW, i fixed a bug with clips (#1178), not related with the issue you reported.

greetings guys @extesy @GrosPoulet

i just tried using hz+ on opera browser now, freshly installed browser that i'd never used, with freshly installed hz+ extension/addon from chrome webstore.

went to kick.com with hz+ active (without placing kick.com as an exception site, ie fully operational on kick.com). and the moment i clicked the kick icon on top left of screen, to essentially refresh the page, instantly opera gave me a 'bad request' blank page.

the issue still exists. I personally never mentioned something about clips, my main issue was that the website itself seems to break completely, with hz+ active/on. I thought i'd made this clear in my original issue report, and that the issue was understood and had been fixed as stated for this current (new) version.

I'm not sure why the issue isn't 'reproducible'. it's a fresh install of hz+ off of chrome webstore.

https://www.reddit.com/r/brave_browser/comments/13opjk9/400_bad_request_kickcom_kickstreaming_error_fix/?sort=new

i would recommend scanning the comments underneath my reddit post, when i first encountered this problem. there are several people citing this as an issue in exactly the same way i'm experiencing it. having deactivated hz+ their browsing on kick.com is now without issue.

[GrosPoulet]

@eitaniel i did exactly the same: fresh install on Opera: it works perfectly. I can also read videos from Google search page (search for: site:kick.com/video) Opera: 100.0.4815.84 Win 10 Pro 22H2 build: 19045.3208

[eitaniel]

@GrosPoulet thanks for feedback

were you able to look at the reddit link i posted at the end of my last message, showing that several people, even until recently, still have this problem? i think the issue probably manifests itself when people log into their kick.com accounts. i tried using a freshly 'reinstalled' hz+ on brave browser a few minutes ago, and found, before logging into my kick.com account that things SEEMED fine. for a minute or two. after logging in, with my credentials, i found that within 1 minute, the 404 bad request error popped up and the site was thereafter totally inaccessible.

https://www.reddit.com/r/brave_browser/comments/13opjk9/400_bad_request_kickcom_kickstreaming_error_fix/?sort=new

BRAVE: Version 1.56.14 Chromium: 115.0.5790.114 (Official Build) (64-bit) OS Name Microsoft Windows 10 Pro Version 10.0.19045 Build 19045

EDIT:

1 minute ago (13h05, south african time), i have just surfed kick.com without logging in. this time i made sure to surf for a few minutes, about 3-5 minutes. i clicked around the site, visiting stream after stream, clicking on 'browse', clicking on 'kick beta' on the top left of the page, etc., generally navigating the site. within 5 minutes, the 404 bad request error popped up. this time I didn't log into my account. the error is still being generated. it surely can't just be me and the other users on the reddit post above that are having this issue.

[JoshLambda]

Same problem.

OS: Windows 10 Browser: Google Chrome Version 115.0.5790.110 (Official Build) (64-bit) HZ+: Version 1.0.207

• With HZ+ installed it's impossible to access kick.com, only getting errors 400/404.
• It works again when adding kick.com to exclude list in HZ+ settings AND clearing cookies.
• When removing kick.com from exclude list it keeps working for ~10 minutes then the errors appear again.

I can repeat the issue with 100% accuracy using the process above.

[eitaniel]

Same problem.

OS: Windows 10 Browser: Google Chrome Version 115.0.5790.110 (Official Build) (64-bit) HZ+: Version 1.0.207

• With HZ+ installed it's impossible to access kick.com, only getting errors 400/404.
• It works again when adding kick.com to exclude list in HZ+ settings AND clearing cookies.
• When removing kick.com from exclude list it keeps working for ~10 minutes then the errors appear again.

I can repeat the issue with 100% accuracy using the process above.

thank you @JoshLambda for confirming that i'm not losing my mind! lol

[extesy]

@GrosPoulet Since clearing cookies fixes the problem, I suspect it might be related to the "header rewrite" feature which is caching some headers that break Kick and it becomes impossible to unbreak it without removing those cached values. Maybe it's only some videos that do this, or maybe Kick has some kind of site protection that changes header behavior over time.

[eitaniel]

interesting.

what i've found is happening now is that after i've checked the box of the feature @extesy has mentioned above ("Allow rewrite of headers for HTTP(S) request or response"), kick.com doesn't break in the same manner it has previously.

what happens now is that kick.com logs me out after a few minutes of browsing, but i dont get the 404/400 bad request error anymore, even after several clicks over a period of time, of the "kick beta" header.

prior to this, i had never ticked the box for the headers feature. ever. it was 'inactive' as a feature on my personal use of hz+. after extesy mentioned the feature, i tried activating it and seeing what results i'd get, which are described above.

[GrosPoulet]

@eitaniel @JoshLambda I still did not managed to reproduce this issue. => could you please try to find out which cookie triggers the logout ? You might let DevTools window opened with Kick.com cookies displayed as you surf the site. As soon as you get logged out, check which cookie was added/modified. Plug-in for kick.com might be able to patch it on the fly to prevent logout.

[extesy]

I think cookies is a red herring here. When you clear cookies for a site, you also clear local storage: @GrosPoulet The storeHeaderSettings is suspect, not the cookies. But I could be wrong, of course.

[eitaniel]

@extesy @GrosPoulet

greetings

i've noted the updated version (1.0.209)

to start, with hz+ active on kick.com, and "allow rewrite of headers..." feature also active (box ticked), i was able to surf the site without problem for an extended period.

however, when i deactivated "headers" feature, almost instantly got logged out. site surfing was still fine, but logging out became regular each time i subsequently logged in.

completely deactivating "headers" feature totally results in site breakage. 400/404 bad request error. so that's still very much the case, without activating "headers" feature of hz+, the site breaks within seconds, or minutes/mins.

i've posted as many screenshots as possible, with DEV TOOLS active, hoping there's something evident you can see as developers (i'm an absolute layman with coding and dev stuff, so i dont know what i'm seeing or 'reading')

i hope something can be understood from the screens. thanks for continuously engaging me on this issue, it's a weird one and i can't seem to convey exactly what my experience is to help you understand why it's happening with me, but for some reason it's not happening when you guys try to reproduce.

cheers

[extesy]

@eitaniel To help me understand the use case, why did you disable "header rewrite" if the site works perfectly fine with this setting enabled?

[eitaniel]

@extesy it's not that the site 'works perfectly', the site logs me out with "headers rewrite" enabled.

hence, i can't use the site with my personal account, ie can't use my dashboard, can't see my 'followed' creators to the left panel of kick's site, as well as any other personalized experience offered by kick with a personal account.

the site 'functions' decently ("normally") without generating the 400/404 bad request error, which basically makes the site inaccessible once generated.

i was testing how the site would respond to hz+ if "headers rewrite" was enabled, and thereafter, disabled.

"headers rewrite" enabled = site doesn't completely break, no 400/404 bad request error, general surfing, NO PERSONAL ACCOUNT ACCESSIBILITY (logs me off the site after few seconds/mins)

"headers rewrite" disabled = after few seconds/mins, kick.com breaks completely, inaccessible. 404/400 bad request site error generated. deleting cookies and rebooting site, temporarily restores kick.com, thereafter, with few mins browsing, site breaks again.

[Jd-19]

Same issue for me for several weeks now. Same "400 bad request" error

[eitaniel]

is there any other way that we can help the devs clearly identify what could be happening here for several people, between this github thread, and my post on reddit with similar comments?

@extesy @GrosPoulet