{"id":4735,"date":"2009-03-28T00:10:57","date_gmt":"2009-03-28T00:10:57","guid":{"rendered":"http:\/\/alienbabeltech.com\/main\/?p=4735"},"modified":"2009-03-28T00:17:58","modified_gmt":"2009-03-28T00:17:58","slug":"longer-urls-wasting-74mbits-of-bandwidth","status":"publish","type":"post","link":"https:\/\/alienbabeltech.com\/main\/longer-urls-wasting-74mbits-of-bandwidth\/","title":{"rendered":"Longer URL’s wasting 74Mbit\/s of bandwidth ?"},"content":{"rendered":"

This should get the attention of all the web-developers and administraors out there (ours too<\/em> !<\/em>).\u00a0 John Buswell writes “Overlooking the obvious, web developers and content management systems using long file and path names are wasting bandwidth. While these are handy to identify and manage objects, they increase the length of HTTP requests, force extra processing on Application Delivery Controllers and waste bandwidth. We look at simple and yet creative ways to reduce bandwidth costs for high traffic sites.” <\/em><\/span><\/p>\n

In his article<\/a> he looks at techniques a web developer can use to improve the performance of their high traffic web site and how long URL’s are wasting bandwidth. <\/span><\/p>\n

To understand this problem we need to understand the basics:<\/span><\/p>\n

\n

Basics: The HTTP GET Request<\/span><\/span><\/h4>\n

When a client visits a web site, regardless of whether they click on a link or type the URL directly into their browser, they generate what is called a GET request. The initial GET request pulls down the HTML file, which is then processed, and subsequent links generate new HTTP GET requests, such as CSS, Javascript or Images. The longer the PATH to those links, the larger the HTTP GET request will be. Using telnet we can simulate a HTTP GET request. Here is an example to o3magazine.com. <\/span><\/span><\/p>\n

<\/span><\/span><\/p>\n


<\/span><\/p>\n

\n

<\/span><\/span><\/p>\n


<\/span><\/p>\n