User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > 414 Request-URI Too Large - NOT A BUG - CLOSED
Page:
 
dbreeze
offline
Link
 
I bump into this regularly because I use a fat DC. All you have to do is pull extra depth players until it updates correctly. A re-order is not required unless you can't figure out who to pull and want Bort to do your DC for you. Just a small bump in the total # of DC players allowed(if possible) would fix most of these errors.
Also note it's a UR(I) error, not UR(L). Uniform Resource Index/Indicator? vs, Locator. I think.
 
TruthHammer
Lead Bugs Mod
offline
Link
 
Originally posted by dbreeze
All you have to do is pull extra depth players until it updates correctly. A re-order is not required unless you can't figure out who to pull and want Bort to do your DC for you. Just a small bump in the total # of DC players allowed(if possible) would fix most of these errors.


This problem happens in 2 separate instances. One is when your DC is very large, and in that case, your solution works (though it's still a bug).

It also happens to new owners who have just purchased a team and are saving their DCs for the first time regardless of the DC size. This seems to be the most common issue (or at least the most commonly reported). The fact that it's been blown even though it mostly affects people who are new to the game (or at least new to team ownership) is one of the most disturbing aspects of this issue.

Originally posted by dbreeze
Also note it's a UR(I) error, not UR(L). Uniform Resource Index/Indicator? vs, Locator. I think.


A URL is a subset of a URI. The link in question both a URL and a URI, but let's stay on topic.
Edited by TruthHammer on Nov 11, 2010 15:18:20
 
guardian__J
offline
Link
 
+1 to everything TruthHammer said.

As a Lead Software Developer that is responsible for teaching/enforcing others to do proper error handling, it is extremely offensive to say this isn't a bug. ANYTIME you write code that allows a situation in which the server throws an error message, it is most DEFINITELY a bug. But, obviously, writing in a way that this would never happen IS impossible. However, when you know what the error is, you know why it happens, you know exactly what circumstance causes it, it is clearly your responsibility to trap for that particular incident and show a friendly error message that explains to the user what has happened and how they can resolve it/prevent it on their own. Bort doesn't HAVE to rewrite the page to stop it from wanting to submit a completely incorrect URI (URL), but it should do a check before the submission to see if the error is going to happen and then show an error instead. That would take 5min. of effort. This is baffling because it constantly causes problems for new users who are wanting to spend more money on the game and is very low hanging fruit to correct.
 
VolBrian
Rocky Top
offline
Link
 
Ok, I probably should have done this a while ago, but I've been a little busy.

This has already been sent up and determined not a bug here: http://goallineblitz.com/game/forum_thread.pl?thread_id=4283771

I gave it the "not likely" tag out of habit/procedure. It is not considered a bug.

Closing as not a bug

 
Page:
 


You are not logged in. Please log in if you want to post a reply.