Hi! I’m Benjamin Carter. I see you’re having trouble opening the Fleaflicker Fantasy Leagues app. Just to get us started—are you having issues opening the app on your Windows device, or is it the website that won’t open on your WebKit browser? Also, do you get any error messages, or does it just fail to load?

Meanwhile, here are some initial steps to try that often solve app or site loading problems:

1. Restart your device. This can clear up temporary glitches.
2. Clear your browser cache and cookies since old data can sometimes block loading.
3. Make sure your browser is updated to the latest version—that helps with compatibility.
4. Try accessing Fleaflicker in a private/incognito window or a different browser to see if it’s a browser-specific issue.
5. If using the app, ensure the app is updated to the latest version from the store.
6. Check your internet connection to be sure it is stable.

If you’ve tried any of these already or still get no luck, please let me know any specific details you notice. That way, I can guide you with more targeted steps or check for known issues on Fleaflicker’s end.

Type Exception Report

Message Request header is too large

Description The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

Exception

java.lang.IllegalArgumentException: Request header is too large org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:767) org.apache.coyote.http11.Http11InputBuffer.parseHeader(Http11InputBuffer.java:961) org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:590) org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:293) org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:935) org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1826) org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1189) org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:658) org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63) java.base/java.lang.Thread.run(Thread.java:

Thanks for sharing that detailed error message! The "Request header is too large" error generally means the server is rejecting your request because the HTTP headers—small chunks of information sent by your browser—are exceeding the size limit. This often happens if cookies or other stored data have become too large or corrupted.

Here's how you can fix this on your Windows device using your WebKit browser:

1. Clear Your Browser’s Cookies and Cached Data:
Sometimes cookies or saved site data related to Fleaflicker can grow too big. Clearing those will reset things and allow the headers to stay within limits.
- Go to your browser's settings
- Find "Privacy" or "Clear browsing data"
- Select cookies and cached files (you can keep passwords saved if you want)
- Clear them and restart the browser

2. Try Opening Fleaflicker in a Private or Incognito Window:
This mode doesn't use stored cookies or data, so if the site opens fine this way, it confirms the issue is related to stored browser data.

3. Reduce Stored Cookies by Logging Out of Unused Sites:
If you often visit many websites, consider logging out or clearing cookies for sites you no longer use, which can reduce header size overall.

4. Check for Browser Extensions:
Sometimes extensions can add extra headers. Try disabling them temporarily to see if the problem resolves.

5. Try a Different Browser:
If the issue persists, try accessing Fleaflicker with a different browser like Chrome, Firefox, or Edge.

If you’d like, I can guide you step-by-step on clearing cookies in your specific WebKit-based browser on Windows 10. Would that help?

Are you able to try these and let me know if the problem gets resolved?