I'm a new member and I joined specifically for the analytical capabilities of your engine and its ability to spot things like missed opportunities to win.
When I attempt to view those details, your site generates nginx errors, URI too large etc.
Can someone look into this?
How about a screenshot?
I'll grab one next time it occurs.
It's a nginx 411 error - it should be in your nginx logs.
I mean, a screenshot is not useful. It's just text saying "414 Request-URI Too Large". This is the entire page source:
<html> <head><title>414 Request-URI Too Large</title></head> <body> <center><h1>414 Request-URI Too Large</h1></center> <hr><center>nginx</center> </body> </html>
This is a problem with the server. Firefox vs chrome doesn't make a difference. (I'm getting it on Firefox.) It's not super surprising; some of the URIs are in excess of 10,000 characters.
That's incorrect. This is not a client-side error - it's an infrastructure error generated by the nginx server. It would happen regardless of browser used.
Also - I work in IT and know that if this were happening with any product I were responsible for, I'd want to know immediately so that I could correct the issue.
How do we get this to the right people? I'm new here, and don't know who to reach out to or how. If they're not already aware of this, they should be.
> if this were happening with any product I were responsible for, I'd want to know immediately so that I could correct the issue.
… especially one people are paying for.
Also - I work in IT and know that if this were happening with any product I were responsible for, I'd want to know immediately so that I could correct the issue.
How do we get this to the right people? I'm new here, and don't know who to reach out to or how. If they're not already aware of this, they should be.
https://support.chess.com/collection/343-contact-us
But you would need to provide a link to the resource you were trying to reach or what exactly you were doing when it happened. I could be wrong, but the site has enough traffic that by the time support gets to the ticket, there is a chance there won't be a useful log to look at.
Hey,
So I'm new here but work in IT / security.
This happens because the redirect to the "analysis" functionality (https://www.chess.com/analysis) uses a GET request, where the game data is passed in the URL/address bar (https://www.chess.com/analysis?[...game data here..]).
This is fine in most cases, but when a significantly large amount of data needs to be sent (i.e when you have a lengthy game) there is more data than what is allowed to be passed in a URL resulting in the 414 "URI too long error" error from the server.
All servers have a reasonable limit on how much data can be passed in the URL - for example the Apache server can only process a URL up to a max of 8190 bytes in length - and because of this limitation if you want to send a large amount of data, you would instead need to use a POST request - where the data is sent in the request "body" (free of this limitation) rather than the request URL.
An example of the difference is when you log in for example. You don't see your username and password in the address bar because it's being passed in a POST request to the server rather than a GET.
Not sure on the appropriate routes to report technical issues on the site, but I used the link above to submit a support ticket with some evidence and an example URL that causes the error.
Hopefully they can get it sorted.
I agree and find it strange that they'd attempt to send the entire game as a parameter to a GET rather than using an HTTP POST.
As a band-aid until they move to POSTs, they could increase the nginx large_client_header_buffers value. How large? They can search their logs and see! They have all the data they need to know how large these requests can get, because this error is logged server-side. Personally, seeing as the length of the URI is driven by the number of moves made in a match, it's inherently unconstrained (a player can make any number of moves in the course of a match), so a POST makes a lot more sense long-term.
I'm annoyed that we (users) are brainstorming solutions to a problem that chess.com staff won't even acknowledge exists. This is my second forum post on this topic, and I've previously submitted a bug report too. All unacknowledged by their staff.
I was just having the same problem -- but I found a workaround. At the end of (or at any point during) the game, you can click on the "Download" button, and you'll have the ability to view the PGN for the game. Copy the PGN. Then visit https://www.chess.com/analysis, where you can click "Load PGN". Paste the PGN that you copied, and click "Load". Voila! (Or at least it works for me.)
Forbidden
You don't have permission to access /images/ on this server.
Apache/2.2.3 (CentOS) Server at www.chess.net Port 80
That's not even this website.
I'm a new member and I joined specifically for the analytical capabilities of your engine and its ability to spot things like missed opportunities to win.
When I attempt to view those details, your site generates nginx errors, URI too large etc.
Can someone look into this?