Calguns.net  

Home My iTrader Join the NRA Donate to CGSSA Sponsors CGN Google Search
CA Semiauto Ban(AW)ID Flowchart CA Handgun Ban ID Flowchart CA Shotgun Ban ID Flowchart
Go Back   Calguns.net > SPECIALTY FORUMS > FFL's Forum
Register FAQ Members List Calendar Mark Forums Read

FFL's Forum For open discussion between FFLs and polite questions for FFLs.

Reply
 
Thread Tools Display Modes
  #1  
Old 01-09-2013, 2:13 PM
ptoguy2002's Avatar
ptoguy2002 ptoguy2002 is offline
Veteran Member
 
Join Date: Jul 2006
Location: The OC.
Posts: 3,638
iTrader: 37 / 100%
Default ATF EZ Check: 413 Request Entity Too Large ?????

I've sold a receiver, and have the FFL's info, tried checking yesterday and today, and keep getting:

Quote:
413 Request Entity Too Large
HTTP/1.1 413 Request Entity Too Large Date: Wed, 09 Jan 2013 23:07:49 GMT Server: Oracle-Application-Server-10g Connection: close Transfer-Encoding: chunked Content-Type: text/html; charset=iso-8859-1
Request Entity Too Large
The requested resource
/fflezcheck//fflSearch.do;jsessionid=0afbfaf930d73532f8d08ae947 ddb6e193478ff30972.e34PaNePb3iTb40LbhqSaN0Rc3n0
does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit.

Additionally, a 413 Request Entity Too Large error was encountered while trying to use an ErrorDocument to handle the request.

First time I've ever had a problem.
Anybody ever run across this?
Server problem?
High demand?
Wait?
__________________
WTB: HK21A1 & HK13E parts
WTB: Project & fixer upper guns: Old beaters needing some TLC, C&Rs, Mauser's, Colt's, Beretta's, & HK's
Reply With Quote
  #2  
Old 01-09-2013, 2:27 PM
Toby's Tactical's Avatar
Toby's Tactical Toby's Tactical is offline
Member
 
Join Date: Oct 2012
Posts: 239
iTrader: 0 / 0%
Default

I saw this yesterday also. Couldn't get a different result.
Reply With Quote
  #3  
Old 01-09-2013, 2:27 PM
lazyworm's Avatar
lazyworm lazyworm is offline
Senior Member
 
Join Date: Jan 2006
Location: Dublin, CA
Posts: 1,435
iTrader: 54 / 100%
Default

I don't know about the ez check site, but this error usually means there
is a problem between your browser and that web server.

Try...
* completely clear the forms, re-type all the info and resubmit -- it's possible you have cut-n-pasted too much into the form
* restart browser
* different browser
* flush cache
* different computer
Reply With Quote
  #4  
Old 01-09-2013, 2:31 PM
ptoguy2002's Avatar
ptoguy2002 ptoguy2002 is offline
Veteran Member
 
Join Date: Jul 2006
Location: The OC.
Posts: 3,638
iTrader: 37 / 100%
Default

Tried again (multiple times), and it worked finally.
I think their server is busy.
__________________
WTB: HK21A1 & HK13E parts
WTB: Project & fixer upper guns: Old beaters needing some TLC, C&Rs, Mauser's, Colt's, Beretta's, & HK's
Reply With Quote
  #5  
Old 01-09-2013, 3:05 PM
67goat 67goat is offline
Senior Member
 
Join Date: Apr 2012
Posts: 842
iTrader: 5 / 100%
Default

This is a generic (though fairly uncommon) error describing a connection issue between your browser and their database (I'm not an ffl, but I know a thing or two about web programming).

As more than one person reported this and you didn't say this form was significantly different than others you have submitted, it was most likely on their end. The server being busy could be the reason, but a request timeout error is more common for that. It could also have been that they changed a parameter on that page incorrectly and caused data to be submitted incorrectly. We had a situation at work the other day where certain pages would not work for people logged in with usernames that had a space in them. We made a change and forgot to properly parse usernames, the spaces then broke the code. They could have also made a change that altered how the page excepts data (there are two methods, GET & POST, and they can't always be used interchangeably).

There are only four things you can really look at on your end if that particular error happens. Clear your cache and cookies, make sure there are no fields that exceed the maximum length allowed, no files attached larger than allowed (don't even know if that is possible in this instance), and completely close all browser windows then restart the browser (not the computer, just the program). The last step would close any sessions you had running ang create new connections to any site you were using. The cookies and uploaded files are the most likely culprit if the error is from the client side (your browser). The field length issue is possible, but a stretch (normally this would be a different error, but could be depending on how they coded the page). If all of those are fine on your end, then the error is their system and is not really specific enough to tell you what it is. Also there would be nothing you could do but wait to see if it resolves or contact them to let them know. In this case it seems to have resolved (at least for now).

Web errors (404, 500, 413, etc...) are generally about as useful as you telling you doctor you have a cough. This one has a little more info that would allow somebody with direct access to the server to get a little more info, but it would also be cryptic and mostly useless.
Reply With Quote
  #6  
Old 01-09-2013, 3:17 PM
Librarian's Avatar
Librarian Librarian is offline
Super Moderator
CGN Contributor - Lifetime
 
Join Date: Oct 2005
Location: Concord
Posts: 32,771
iTrader: 4 / 100%
Blog Entries: 6
Default

Quote:
Server: Oracle-Application-Server-10g Connection: close Transfer-Encoding: chunked Content-Type: text/html; charset=iso-8859-1
Request Entity Too Large
says it's an Oracle database error returned because the web app tried to pass it something it didn't like.

The web app detects the Oracle error, and generates its own set.

In this case, I'd say the same as all the first-line (rabbit) tech support people do - 'have you closed and restarted your program? Have you rebooted your computer?'

('rabbit' is a 'get there quick' technician; service contracts usually have a minimum response time in them - one pays more for shorter time [extreme version is a tech that lives at your site 24/7]. Doesn't matter to the contract terms if the person who shows up can't fix the problem, some body showed up to meet the response time.)
__________________
Calguns Wiki, Magazine Qs, Knife laws

Unless there is some way to amend a bill so you would support it,
the details do not matter until the Governor signs or allows the bill to become law.

Ask CA law questions in the How CA Laws Apply to/Affect Me Forum
- most questions that start 'Is it legal ...' go there.

Not a lawyer, just Some Guy On The Interwebs.


Reply With Quote
  #7  
Old 01-09-2013, 7:41 PM
67goat 67goat is offline
Senior Member
 
Join Date: Apr 2012
Posts: 842
iTrader: 5 / 100%
Default

The "Request Entity Too Large" part of that is not an Oracle message. It's an HTTP error description for a 413 error. It does not indicate specifically that it is a database error (though it very well could be). It is a web application error page used for debugging. The web app should be configured so an end user never sees that message (can give too much information about system design and connection settings). Any error page for a web app will show a connection line like that. Our debug pages show a MSSQL line even when the error is a code issue and not a database error, but we use a custom error page so the user would never see that line.
Reply With Quote
  #8  
Old 01-09-2013, 8:35 PM
TRICKSTER's Avatar
TRICKSTER TRICKSTER is offline
I need a LIFE!!
 
Join Date: Mar 2008
Location: Contra Costa County
Posts: 10,823
iTrader: 15 / 100%
Default

You can always look it up manually.
http://www.atf.gov/about/foia/ffl-list-2012.html
__________________


Ignorance can be educated.
Crazy can be medicated.
But there is no cure for stupid.


Police Brutality? https://www.youtube.com/watch?v=nRd5oucG114

NRA Benefactor Member

Last edited by TRICKSTER; 01-09-2013 at 8:38 PM..
Reply With Quote
  #9  
Old 01-09-2013, 8:55 PM
Librarian's Avatar
Librarian Librarian is offline
Super Moderator
CGN Contributor - Lifetime
 
Join Date: Oct 2005
Location: Concord
Posts: 32,771
iTrader: 4 / 100%
Blog Entries: 6
Default

The actual Oracle message appears to be
Quote:
DRG-11832 Request Entity Too Large
Cause:

Request rejected because request entity is too large (HTTP_ERROR = 413).
http://ora-messages.adgoogy.com/DRG-11832

Sigh; typical damned error message. Once had a DB throw an error substantially 'this should never happen'; printed my screen, took it down to the developer, and said, 'So, Ed, about this message ... '. Worked for Ingres, Sybase, Informix in software testing in a previous life.
__________________
Calguns Wiki, Magazine Qs, Knife laws

Unless there is some way to amend a bill so you would support it,
the details do not matter until the Governor signs or allows the bill to become law.

Ask CA law questions in the How CA Laws Apply to/Affect Me Forum
- most questions that start 'Is it legal ...' go there.

Not a lawyer, just Some Guy On The Interwebs.


Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump



All times are GMT -8. The time now is 9:56 PM.




Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2016, vBulletin Solutions, Inc.
Proudly hosted by GeoVario the Premier 2A host.
Calguns.net, the 'Calguns' name and all associated variants and logos are ® Trademark and © Copyright 2002-2016, Calguns.net an Incorporated Company All Rights Reserved.