Computer Networks and ISDN Systems
Network performance effects of HTTP/1.1, CSS1, and PNG
SIGCOMM '97 Proceedings of the ACM SIGCOMM '97 conference on Applications, technologies, architectures, and protocols for computer communication
Key differences between HTTP/1.0 and HTTP/1.1
WWW '99 Proceedings of the eighth international conference on World Wide Web
N for the price of 1: bundling web objects for more efficient content delivery
Proceedings of the 10th international conference on World Wide Web
Proceedings of the 2001 conference on Applications, technologies, architectures, and protocols for computer communications
On the use and performance of content distribution networks
IMW '01 Proceedings of the 1st ACM SIGCOMM Workshop on Internet Measurement
Clarifying the fundamentals of HTTP
Proceedings of the 11th international conference on World Wide Web
Aliasing on the world wide web: prevalence and performance implications
Proceedings of the 11th international conference on World Wide Web
Flash crowds and denial of service attacks: characterization and implications for CDNs and web sites
Proceedings of the 11th international conference on World Wide Web
Refreshment policies for web content caches
Computer Networks: The International Journal of Computer and Telecommunications Networking
Looking for Science in the Art of Network Measurement
IWDC '01 Proceedings of the Thyrrhenian International Workshop on Digital Communications: Evolutionary Trends of the Internet
Using bundles for Web content delivery
Computer Networks: The International Journal of Computer and Telecommunications Networking
Automated analysis of P3P-enabled Web sites
ICEC '03 Proceedings of the 5th international conference on Electronic commerce
Characterization of a large web site population with implications for content delivery
Proceedings of the 13th international conference on World Wide Web
Clarifying the fundamentals of HTTP
Software—Practice & Experience - Special issue: Web technologies
Managing the Performance Impact of Web Security
Electronic Commerce Research
DHTTP: an efficient and cache-friendly transfer protocol for the web
IEEE/ACM Transactions on Networking (TON)
Computer Networks: The International Journal of Computer and Telecommunications Networking
Energy-aware QoS for application sessions across multiple protocol domains in mobile computing
Computer Networks: The International Journal of Computer and Telecommunications Networking
Computer Networks: The International Journal of Computer and Telecommunications Networking
Web timeouts and their implications
PAM'10 Proceedings of the 11th international conference on Passive and active measurement
A longitudinal view of HTTP traffic
PAM'10 Proceedings of the 11th international conference on Passive and active measurement
Proceedings of the 16th Conference on Pattern Languages of Programs
Tradeoffs for web communications fast analysis
NETWORKING'05 Proceedings of the 4th IFIP-TC6 international conference on Networking Technologies, Services, and Protocols; Performance of Computer and Communication Networks; Mobile and Wireless Communication Systems
| Hi-index | 0.03 |
With the recent (draft) standardization of the Hypertext Transfer Protocol - HTTP/1.1 protocol on the Web, it is natural to ask what percentage of popular Web sites speak HTTP/1.1 and how compliant are these so-called HTTP/1.1 servers. We attempt to answer these questions through a series of experiments based on the protocol standard. The tests were run on a comprehensive list of popular Web sites to which a good fraction of the Web traffic is directed. Our experiments were conducted on a global extensible testing infrastructure that we built to answer the above questions. The tests were carried out over a period of 16 months and were repeated thrice during the period. Our results show reasons for concern on the state of HTTP/1.1 protocol compliance: some servers do not properly support basic features such as the HEAD method, while many popular servers do not support some of the key features (such as persistent connections) that were added in HTTP/1.1. Perhaps most alarming of all, some servers crashed during testing. As a result we believe that small (but significant) changes to the wording of the protocol specification are required.