• The KIPS Transactions:PartC
• /
• v.9C no.4
• /
• pp.605-614
• /
• 2002

Amount of the web traffic web server handles are explosively increasing, which requires that the performance of the web server should be improved for the various web services. Although the analysis for the HTTP traffic with the proper tuning for the web server is essential, the research relevant to the subject are insignificant. In particular, although most of applications are implemented over HTTP 1.1 protocol, the researches mostly deal with the performance evaluation of the HTTP 1.0 protocol. Consequently, the modeling approach and the performance evaluation over HTTP 1.1 protocol have not been well formed. Therefore, basing on the HTTP 1.1 protocol supporting persistent connection, we present an analytical end-to-end tandem queueing model for web server to consider the specific hardware configuration inside web server beginning at accepting the user request until completing the service. we compare various performances between HTTP 1.0 and HTTP 1.1 under the overloading condition, and then analyze the characteristics of the HTTP traffic that include file size requested to web server, the OFF time between file transfers, the frequency of requests, and the temporal locality of requests. Presented model is verified through the comparing the server throughput according to varying requests rate with the real web server. Thereafter, we analyze the performance evaluation of the web server, according to the interrelation between TCP Listen queue size, the number of HTTP threads and the size of the network buffers.

• Journal of KIISE:Computer Systems and Theory
• /
• v.32 no.11_12
• /
• pp.717-721
• /
• 2005

With HTTP/1.0, a single request means a single HTTP connection so that the granular unit of dispatching is the same as real load. But with persistent HTTP connection, multiple requests may arrive on a single TCP connection. Therefore, a scheme that dispatches load at the granularity of individual requests constrains the feasible dispatching policies In this paper we propose a new connection dispatching polity for supporting HTTP/1.1 persistent connections in cluster-based Web servers. When the request of a base html file arrives, the dispatcher gets the subsequent load arriving on that connection using the embedded objects information. After the dispatcher stores the load information in Load Table, the dispatcher employs the connection aging strategy on live persistent connections on the passage of time. The results of simulation show about $1.7\%\~16.8\%$ improved average response time compared to existing WLC algorithm.

• Journal of the Korea Computer Industry Society
• /
• v.6 no.2
• /
• pp.305-316
• /
• 2005

A heterogeneous webserver such as an HTTP server should be able to currently deal with numerous users. To the end, it is inevitable to formally analyze web traffics as well as a webserver itself. In particular, as most systems adopt HTTP 1.1 protocol instead of HTTP 1.0 protocol, it is more difficult to represent the system as a simple analytic mode. In addition, since most of previous models missed the detailed processes of the server, it is unsuitable for the current server based on HTTP 1.1 to tune itself with its own system parameters. On the basis of HTTP 1.1 Protocol supporting persistent connections, we thus present an analytical end-to-end tandem queueing model considering specific hardware configurations inside the webserver, which ultimately covers from accepting the customer requests to completing the services.

• Annual Conference of KIPS
• /
• 2000.04a
• /
• pp.629-632
• /
• 2000

현재 사용하고 있는 HTTP/1.0은 각각의 트랜잭션마다 별개의 TCP 연결 설정을 해야함으로서 야기되는 잦은 RTT지연과 Slow Start로 인해 성능상의 문제점을 야기하고 있다. IETF의 HTTP-NG은 이런 문제점을 포함하여 다각적인 요구를 수용할 수 있도록 HTTP/1.1(RFC 2616)을 발표하였다. HTTP/1.1은 이 문제점을 지속적인 연결(Persistent Connection) 개념을 도입하여 개선하고 있다. 그러나, 연결 해제 시점을 명확하게 정의하고 있지 않기 때문에 이로 인해 서버의 자원 낭비를 줄이는 효율적인 연결 관리 방법을 제시하지 못하고 있다. 본 논문은 하나의 TCP 연결 위에 다중의 요구들을 실행할 수 있는 HTTP/1.1의 지속적인 연결 개념에, 클라이언트 측에서 적절한 TCP 연결 해제 시점을 지원하여 서버 자원을 효율적으로 사용할 수 있는 알고리즘을 제안한다.

• Journal of Broadcast Engineering
• /
• v.24 no.4
• /
• pp.602-612
• /
• 2019

Various streaming technologies are being studied to guarantee the QoE of viewers due to the development of realistic media. HTTP adaptive streaming is a typical example, and it is based on HTTP / 1.1 and TCP. These protocols have become one of the causes of delaying the image delay and increasing the waiting time of web pages. Therefore, in this paper, we propose a QUIC-DASH system applying the UDP-based transmission protocols QUIC and HTTP / 2 to the MPEG-DASH system after analyzing various transmission protocols and development process of HTTP. Through experiments, the QUIC-DASH system confirmed the possibility of providing optimal performance in terms of transmission speed of LTE environment than existing system. We also suggest various future studies for better performance.

• KIPS Transactions on Computer and Communication Systems
• /
• v.10 no.5
• /
• pp.137-144
• /
• 2021

The IETF has recently been standardizing the QUIC protocol for HTTP/3 services. It is noted that HTTP/3 uses QUIC as the underlying protocol, whereas HTTP/1.1 and HTTP/2 are based on TCP. Differently from TCP, the QUIC uses 0-RTT or 1-RTT transmissions to reduce the connection establishment delays of TCP and SCTP. Moreover, to solve the head-of-line blocking problem, QUIC uses the multi-streaming feature. In addition, QUIC provides various features, including the connection migration, and it is available at the Chrome browser. In this paper, we analyze the performance of QUIC for HTTP-based web and streaming services by comparing with the existing TCP and Streaming Control Transmission Protocol (SCTP) in the network environments with different link delays and packet error rates. From the experimental results, we can see that QUIC provides better throughputs than TCP and SCTP, and the gaps of performances get larger, as the link delays and packet error rates increase.

• Journal of KIISE:Information Networking
• /
• v.28 no.1
• /
• pp.126-135
• /
• 2001

HTTP 프로토콜은 WWW에서 HTML(HyperText Markup Language)문서를 송수신하기 위해 사용하고 있는 애플리케이션 프로토콜로서 TCP를 수송계층 프로토콜로 이용하여 이루어지는 애플리케이션 계층 프로토콜 가운데 하나이다[12]. HTTP/1.0은 동일한 서버로부터 각각의 개체에 대하여 개별적인 TCP연결은 생성하기 때문에 다중의 요구를 비효율적으로 처리한다. 이러한 문제를 해결하기 위한 방안으로 제안된 HTTP/1.1은 TCP연결을 지속적인 연결(Persistent connection)이라는 개념을 도입하여 하나의 TCP 연결 상에서 다중의 요구(Request)를 처리하도록 하고 있다[9]. 네트워크가 발전됨에 따라 사용자가 늘어나고 다양해지면서 서비스의 차별화 문제가 중요한 문제로 대두되었다.[3.5] 본논문에서 제시하는 Diff-HTTP은 웹 서버에 서비스를 요청한 클라이언트들에게 차별화 된 서비스를 제공하기 위해서 사용자를 두 등급 기본등급과 우선 순위를 고려한 상위 등급으로 구분한다. 각 등급은 제한시간으로 차별화되고 상위 등급에 속한 클라이언트에게 제한된 시간을 증가 시켜 지연을 최소로 함으로써 고품질의 서비스를 제공하는 방안을 제시한다.

• Annual Conference of KIPS
• /
• 2002.11a
• /
• pp.481-484
• /
• 2002

원활한 웹서버의 성능유지를 위하여, HTTP 트래픽의 특성에 대한 분석과 웹서버의 적절한 튜닝이 요구되고 있지만 이에 대한 연구는 아직 미진한 상태이다. 특히, 현재 대부분의 어플리케이션이 HTTP 1.1에 기반하여 구현되고 있음에도 불구하고, 대부분의 연구들이 HTTP 1.0에 기반하여 성능 분석이 이루어진 반면 HTTP 1.1에 대한 모델링과 성능분석은 거의 이루어지지 못하였다. 따라서, 본 논문에서는 지속연결을 지원하는 HTTP 1.1 프로토콜을 기반으로 하여 서버내의 세부 하드웨어 특성 등을 고려하여, 웹서버가 사용자의 요청을 받아들이면서부터 서비스를 마칠 때까지의 과정을 Tandem 네트워크 큐잉 모델을 사용하여 해석적인 웹서버 모델을 제안한다.

• Journal of KIISE
• /
• v.44 no.1
• /
• pp.1-12
• /
• 2017

The continuously growing internet service requirements has resulted in a multitier system structure consisting of web server and database (DB) server. In this multitier structure, the existing intrusion detection system (IDS) detects known attacks by matching misused traffic patterns or signatures. However, malicious change to the contents at DB server through hypertext transfer protocol (HTTP) requests at the DB server cannot be detected by the IDS at the DB server's end, since the DB server processes structured query language (SQL) without knowing the associated HTTP, while the web server cannot identify the response associated with the attacker's SQL query. To detect these types of attacks, the malicious user is tracked using knowledge on interaction between HTTP request and SQL query. However, this is a practical challenge because system's source code analysis and its application logic needs to be understood completely. In this study, we proposed a scheme to find the HTTP request associated with a given SQL query using only system log files. We first generated an HTTP request-SQL query map from system log files alone. Subsequently, the HTTP request associated with a given SQL query was identified among a set of HTTP requests using this map. Computer simulations indicated that the proposed scheme finds the HTTP request associated with a given SQL query with 94% accuracy.

• Journal of the Korea Institute of Information Security & Cryptology
• /
• v.21 no.3
• /
• pp.45-56
• /
• 2011

Hyper Text Transfer Protocol(HTTP) is widely used in nearly every network when people access web pages, therefore HTTP traffic is usually allowed by local security policies to pass though firewalls and other gateway security devices without examination. However this characteristic can be used by malicious people. With the help of HTTP tunnel applications, malicious people can transmit data within HTTP in order to circumvent local security policies. Thus it is quite important to distinguish between regular HTTP traffic and tunneled HTTP traffic. Our work of HTTP tunnel detection is based on Support Vector Machines. The experimental results show the high accuracy of HTTP tunnel detection. Moreover, being trained once, our work of HTTP tunnel detection can be applied to other places without training any more.