webserver overload
Download as DOCX, PDF2 likes1,526 views
A web server can become overloaded due to high legitimate web traffic, denial of service attacks, computer worms causing abnormal traffic, viruses infecting browsers and servers, unfiltered internet bots, network slowdowns, and partial server failures. Symptoms of overload include requests being served slowly, HTTP error codes being returned, TCP connections being refused or reset, and in rare cases only partial content being returned. To prevent overload, sites use techniques like managing network traffic with firewalls and traffic shaping, deploying web caches, using multiple domain names and servers to separate content types, load balancing across multiple servers, and optimizing server software.
webserver overload
- 1. Listandexplainsomefactorthatcan overloada webserver? Web server A web server is a computer system that processes requests via HTTP, the basic network used to distribute information on the World Wide Web. The term can refer either to the entire system, or specifically to the software that accepts and supervises the HTTP requests The most common use of web servers is to host websites, but there are other uses such as gaming, data storage, running enterprise applications, handling email, FTP, or other web uses. Causes of overload
- 2. At any time web servers can be overloaded because of: Too much legitimate web traffic. Thousands or even millions of clients connecting to the web site in a short interval, e.g. Slashdot; Distributed Denial of Service attacks. A denial-of-service attack (DoS attack) or distributed denial-of-service attack (DDoS attack) is an attempt to make a computer or network resource unavailable to its intended users; Computer worms that sometimes cause abnormal traffic because of millions of infected computers (not coordinated among them); XSS viruses can cause high traffic because of millions of infected browsers and/or web servers; Internet bots Traffic not filtered/limited on large web sites with very few resources (bandwidth, etc.); Internet (network) slowdowns, so that client requests are served more slowly and the number of connections increases so much that server limits are reached; Web servers (computers) partial unavailability. This can happen because of required or urgent maintenance or upgrade, hardware or software failures, back-end (e.g., database) failures, etc.; in these cases the remaining web servers get too much traffic and become overloaded.
- 3. Symptoms of overload The symptoms of an overloaded web server are: Requests are served with (possibly long) delays (from 1 second to a few hundred seconds). The web server returns an HTTP error code, such as 500, 502, 503, 504, 408, or even 404, which is inappropriate for an overload condition. The web server refuses or resets (interrupts) TCP connections before it returns any content. In very rare cases, the web server returns only a part of the requested content. This behavior can be considered a bug, even if it usually arises as a symptom of overload. Anti-overloadtechniques To partially overcome above average load limits and to prevent overload, most popular web sites use common techniques like: Managing network traffic, by using:
- 4. Firewalls to block unwanted traffic coming from bad IP sources or having bad patterns HTTP traffic managers to drop, redirect or rewrite requests having bad HTTP patterns Bandwidth management and traffic shaping, in order to smooth down peaks in network usage Deploying web cache techniques Using different domain names to serve different (static and dynamic) content by separate web servers, i.e.: http://images.example.com http://www.example.com Using different domain names and/or computers to separate big files from small and medium sized files; the idea is to be able to fully cache small and medium sized files and to efficiently serve big or huge (over 10 - 1000 MB) files by using different settings Using many web servers (programs) per computer, each one bound to its own network card and IP address Using many web servers (computers) that are grouped together behind a load balancer so that they act or are seen as one big web server Using more efficient computer programs for web servers, etc.