vista
All Solutions
 
vista
Interent Solutions Home
 
vista
Tests
 
vista
Help
 
  arrow Description
  arrow Occurrences
  arrow Solutions and Fixes
  arrow Official Explanation
  arrow Forum Help
  arrow Research this Issue
  arrow Notes
 
Faultwire solutions
  System Commander
Safely and securely run multiple operating systems on one PC!
box_image  
 
 
box_image
Driver Genius
Improve system stability by getting new drivers! Also makes it easy to backup, restore, and remove drivers.
 
  SystemSuite
The Ultimate, All-in-one Suite for PC security, Anti-Virus, Anti-Spyware, Maintenance and Privacy!
box_image  
     
 
 
Internet Solutions
     
 

413

Request Entity Too Large

 
  Description  
     
  Likely in filling out a form, some entry is too long and the server refuses to accept it.   
   
  Occurrences  
     
 
occurance meter
 
 
Frequency is relative to other Internet warnings and errors.
 
   
  Solutions and Fixes  
     
 

Solution 1 of 1 - Reduce Field Contents

solution field

If you have a field that contains a large amount of text, reduce the amount of text and try again.

   
 
transparent
transparent
solves it indicator
risk indicator
effort indicator
 
 
 

 
 
 
   
  Official Explanation  
     
 

The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request.

If the condition is temporary, the server SHOULD include a Retry-After header field to indicate that it is temporary and after what time the client MAY try again.

(From Hypertext Transfer Protocol -- HTTP/1.1)
 
   
  Forum Help  
     
 
Forums on topic

Check out what others say about this issue and review or add your own comments and solutions!

Go to Forums on topic.
 
   
  Research this Issue  
     
 
Getting search results...
 
   
  Notes  
     
  "413 Request Entity Too Large" is supported by most Web Servers.

The four hundred series of errors indicate something was sent to the remote web server incorrectly.

 
     
  While we believe this information up to date and accurate, FAQware is not responsible for any inaccuracies. If you find something that is out of date or inaccurate, please let us know at so we can correct it.