MINIMAL HTTP HEADER FOR TRAFFIC CRITICAL APPLICATIONS

DOI:10.25140/2411-5363-2017-2(8)-123-128

Author:

Kazymyr Volodymyr, Chernihiv National University of Technology (95 Shevchenka Str., 14027 Chernihiv, Ukraine)

Mokrohuz Andrii , Chernihiv National University of Technology (95 Shevchenka Str., 14027 Chernihiv, Ukraine)

Moshel Mykola, Chernihiv National University of Technology (95 Shevchenka Str., 14027 Chernihiv, Ukraine)

Language: english

Annotation:

Urgency of the research. Every year amount of different mobile devices has been growing. Mobile devices are not only smartphones, laptops and tablets. Many single board computers appeared alongside with IoT (internet of things) direction, which allows connecting anything to the Internet. Amount of mobile devices exceeded amount of desktop computers in 2013. Amount of traffic which mobile devices transfer per month was 7*1018 bytes in 2016. This number will only grow and will reach 10.8 * 1018 bytes in 2017. There is no distinction between web applications for mobile devices and desktop computers anymore. Amount of the web applications have been growing every year as well.

Target setting. We propose to use minimum possible configuration of the HTTP header to decrease the data transferred between client and server software applications. This can be useful especially for mobile devices, which work over 3G and 4G networks with limited battery life. Theoretical minimum header configuration was compared against real data, which has been obtained during the experiment. The results of the comparison give us the information about possibility of decreasing HTTP traffic. The fact that text and image information headers are the biggest tells us to concentrate the attention on these two types of information.

Actual scientific researches and issues analysis. Many scientists from all over the world try to come up with different solutions to improve transmission of HTTP traffic in mobile networks. HTTP is scalable application layer protocol which allows high flexibility in terms of data transferring. HTTP is easy to use; it is supported by popular programming languages. Developers choose to use HTTP for creation of different purpose applications. Mostly HTTP is used for creation of web application and application which work in the Internet. With development of 3G and 4G networks, IoT (Internet of Things) gains its popularity, thus many devices can be communicate over the Internet.

Uninvestigatigated parts of general matters defining. There are many directions to decrease amount of HTTP traffic. However, investigation of headers of HTTP is not considered as one of the methods of decreasing amount of the HTTP traffic.

The research objective. We decided to concentrate our attention on HTTP headers to address the issue of HTTP traffic growth. Previous researches have shown that HTTP header can contain unnecessary data, which can be eliminated [3]. In the paper, we compare theoretically possible minimum configuration of HTTP header with HTTP headers received during the experiment. Many of previous researches are concentrated on HTTP protocol itself. However, we concentrate our attention on data, which is transferred using HTTP. We used web debugging tool to investigate the HTTP header.

The statement of basic materials. Under minimal HTTP header configuration, we understand amount of bytes required to deliver the information over HTTP. According to previous researches, HTTP/1.1 is the most popular version of the HTTP, which is used nowadays. All data captured during our experiment was transferred and received over HTTP/1.1 as well. Request and response message formats differ from each other.

Conclusions. In the paper, we identified the minimal HTTP header configuration, which can still be used to transfer valid HTTP messages. Our experimental data shows that header of the real HTTP traffic exceeds the minimal configuration of HTTP header.

However, we understand, that not every type of application, which work via HTTP, require a small HTTP header. Nevertheless, applications, which are installed and running on the mobile devices require additional attention to the amount of an HTTP traffic transferred.

Key words:

HTTP, information, mobile device, protocol

References:

  1. Statistics on mobile usage and adoption to inform your mobile marketing strategy. Retrieved from: http://www.smartinsights.com/mobile-marketing/mobile-marketing-analytics/mobile-marketing-statistics/, [Oct. 15, 2015].

  2. Kazymyr, V., and A. Mokrohuz. "Selecting a base application layer protocol to transfer data in the client-server architecture. " Технічні науки та технології 3 (2016): 182-187.

  3. V. Kazymyr, A. Mokrohuz. “In HTTP(S) potential traffic overhead for mobile devices”, International Journal “Information Theories and Applications”, Vol. 23, Number 4, 2016, pp. 383-393.

  4. R. Chandran and S. Manoharan. "Performance analysis of New Zealand websites using HTTP header values," Proceedings of 2011 IEEE Pacific Rim Conference on Communications, Computers and Signal Processing, Victoria, BC, 2011, pp. 25-30.

  5. Timothy J. McLaughlin (2002)."The Benefits and Drawbacks of HTTP Compression", Department of Computer Science and Engineering, Lehigh University, 19 Memorial Drive West, Bethlehem, PA 18015.

  6. Sehati and M. Ghaderi, "WebPro: A proxy-based approach for low latency web browsing on mobile devices," 2015 IEEE 23rd International Symposium on Quality of Service (IWQoS), Portland, OR, 2015, pp. 319-328.

  7. ICT Facts and Figures 2016. World Telecommunication/ICT Indicators database 2016 (20th Edition/December 2016). Retrieved from: http://www.itu.int/en/ITU-D/Statistics/Pages/publications/ wtid.aspx.

  8. Fiddler. The free web debugging proxy for any browser, system or platform. Retrieved from: http://www.telerik.com/fiddler, [Oct. 26, 2015].

  9. HTTP (HyperText Transfer Protocol). Retrieved from: https://www.ntu.edu.sg/home/ehchua/ programming/webprogramming/HTTP_Basics.html, [Oct. 26, 2016].

  10. Part of Hypertext Transfer Protocol -- HTTP/1.1. RFC 2616 Fielding, et al. Retrieved from: https://www.w3.org/Protocols/rfc2616/rfc2616-sec5.html#sec5, [May. 21, 2017].

  11. Part of Hypertext Transfer Protocol -- HTTP/1.1. RFC 2616 Fielding, et al. Retrieved from: https://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html, [May. 21, 2017].

  12. Pengcheng Jiang; Fang Liu; Huan Wang; Chenyu Li, "Characterizing HTTP Traffic of Mobile Internet Services in Provincial Network," in Intelligent Human-Machine Systems and Cybernetics (IHMSC), 2014 Sixth International Conference on , vol. 1, no., pp. 78-81, 26-27 Aug. 2014.

Download