組み込みプラットフォームでの独自の http サーバーの実装で忙しくしています。技術的には、サーバーは HTTP 1.0 に準拠しているため、クライアントがヘッダー「Connection: Keep-Alive」を送信して接続を開いたままにしておく必要があります。
実装はこんな感じ。投稿をできるだけ短くするために、HTTP ヘッダーを解析してリクエストを実行するコードを削除しました。
int Service_Request(int conn) {
struct ReqInfo reqinfo;
volatile int resource = 0;
int retval = 0;
Req_Result req_result = GOT_REQ;
InitReqInfo(&reqinfo);
/* while we still have HTTP requests to process */
while (req_result == GOT_REQ)
{
/* Get HTTP request, there are 3 different return values:
* GOT_REQ: we got a valid HTTP request
* TIMEOUT_REQ we timed out waiting for a request
* ERROR_REQ there was some error receiving from the socket
* usually because the connection was closed by the peer*/
req_result = Get_Request(conn, &reqinfo);
if ( req_result == TIMEOUT_REQ)
{
/* timed out waiting for the client, exit */
retval = 0;
break;
}
else if (req_result == ERROR_REQ)
{
/* some error, exit */
retval = -1;
break;
}
/* Process the request GET, PUT and POST is supported*/
if (reqinfo.method == GET)
{
/* code to handle GET*/
}
/* PUT and POST are handled in the same way */
else if ((reqinfo.method == PUT) || (reqinfo.method == POST) )
{
/* Code to handle PUT and POST*/
}
else
{
/* not supported, code should never get here */
reqinfo.status = 501;
Return_Error_Msg(conn, &reqinfo);
}
/*Diag_Msg("Client Request: \r\n");
Diag_Msg(reqinfo.clientRequest);*/
/*
* the reqinfo.keep_alive flag will be set to 1 if the
* "Connection: Keep-Alive" header was sent by the client
*/
if(reqinfo.keep_alive == 0)
{
break;
}
reqinfo.keep_alive_max--;
if(reqinfo.keep_alive_max <= 0 )
{
/*
* the connection has been reused for the maxmum amount of times, stop
*/
break;
}
/*
* If we get here, we will clear the memory used for the client request
* and go to the beginning of the while loop to receive another request
*/
Writeline(conn,"\r\n",2);
FreeReqInfo(&reqinfo);
}
FreeReqInfo(&reqinfo);
return (retval);
}
Get_Request 関数は次のようになります。
Req_Result Get_Request(int conn, struct ReqInfo * reqinfo) {
char buffer[MAX_REQ_LINE] = {0};
int rval;
fd_set fds;
struct timeval tv;
/* Set timeout to 5 seconds if this is the first request since the client connected, wait 5 seconds
* Otherwise, wait 5ms */
if(reqinfo->first_request == 1)
{
tv.tv_sec = 5;
tv.tv_usec = 0;
reqinfo->first_request = 0;
}
else
{
tv.tv_sec = reqinfo->keep_alive_timeout;
tv.tv_usec = 0;
}
/* Loop through request headers. If we have a simple request,
then we will loop only once. Otherwise, we will loop until
we receive a blank line which signifies the end of the headers,
or until select() times out, whichever is sooner. */
do {
/* Reset file descriptor set */
FD_ZERO(&fds);
FD_SET (conn, &fds);
/* Wait until the timeout to see if input is ready */
rval = select(conn + 1, &fds, NULL, NULL, &tv);
/* Take appropriate action based on return from select() */
if ( rval < 0 )
{
Diag_Msg("Error calling select() in get_request()");
return (ERROR_REQ);
}
else if ( rval == 0 ) {
/* input not ready after timeout */
return (TIMEOUT_REQ);
}
else {
/* We have an input line waiting, so retrieve it */
memset(buffer,0,MAX_REQ_LINE - 1);
if(Readline(conn, buffer, MAX_REQ_LINE - 1) == -1)
{
return (ERROR_REQ);
}
if(reqinfo->clientRequest == NULL)
{
reqinfo->clientRequest = calloc(MAX_REQ_LINE - 1, sizeof(char));
strncpy(reqinfo->clientRequest,buffer,MAX_REQ_LINE - 1);
}
else
{
strncat(reqinfo->clientRequest,buffer,MAX_REQ_LINE - 1);
}
Trim(buffer);
if ( buffer[0] == '\0' )
break;
if ( Parse_HTTP_Header(buffer, reqinfo) )
break;
}
} while ( reqinfo->type != SIMPLE );
return (GOT_REQ);
}
このサーバーの仕組みを英語で説明すると: サーバーは最初のリクエストを受け取ります。ヘッダーを解析し、「Connection: Keep-Alive」ヘッダーが見つかった場合は、フラグを設定します。サーバーはこの要求の処理を続行します。完了すると、キープアライブ フラグがチェックされます。クリアされている場合、サーバーは接続を閉じます。設定されている場合、サーバーはクリーンアップ操作を実行し、同じ接続を介して別の要求を待機します。等々。
これをcurlでテストしました：
C:\curl>curl -v -H "Connection: Keep-Alive" --data-binary @vid1.bin 10.84.67.129/s1p0:1/vid[1-2].bin
[1/2]: 10.84.67.129/s1p0:1/vid1.bin --> <stdout>
--_curl_--10.84.67.129/s1p0:1/vid1.bin
* About to connect() to 10.84.67.129 port 80 (#0)
* Trying 10.84.67.129...
* connected
* Connected to 10.84.67.129 (10.84.67.129) port 80 (#0)
> POST /s1p0:1/vid1.bin HTTP/1.1
> User-Agent: curl/7.28.1
> Host: 10.84.67.129
> Accept: */*
> Connection: Keep-Alive
> Content-Length: 51200
> Content-Type: application/x-www-form-urlencoded
> Expect: 100-continue
>
* HTTP 1.0, assume close after body
< HTTP/1.0 100 Continue
* HTTP 1.0, assume close after body
< HTTP/1.0 200 OK
< Server: DTSVU v0.1
< Content-Type: text/html
* HTTP/1.0 connection set to keep alive!
< Connection: Keep-Alive
< Keep-Alive: timeout=5, max=10
<
* Connection #0 to host 10.84.67.129 left intact
[2/2]: 10.84.67.129/s1p0:1/vid2.bin --> <stdout>
--_curl_--10.84.67.129/s1p0:1/vid2.bin
* Connection #0 seems to be dead!
* Closing connection #0
* About to connect() to 10.84.67.129 port 80 (#0)
* Trying 10.84.67.129...
* connected
* Connected to 10.84.67.129 (10.84.67.129) port 80 (#0)
> POST /s1p0:1/vid2.bin HTTP/1.1
> User-Agent: curl/7.28.1
> Host: 10.84.67.129
> Accept: */*
> Connection: Keep-Alive
> Content-Length: 51200
> Content-Type: application/x-www-form-urlencoded
> Expect: 100-continue
>
* HTTP 1.0, assume close after body
< HTTP/1.0 100 Continue
* HTTP 1.0, assume close after body
< HTTP/1.0 200 OK
< Server: DTSVU v0.1
< Content-Type: text/html
* HTTP/1.0 connection set to keep alive!
< Connection: Keep-Alive
< Keep-Alive: timeout=5, max=10
<
* Connection #0 to host 10.84.67.129 left intact
* Closing connection #0
ご覧のとおり、curl は次のように述べています。接続 #0 が停止しているようです。最初のリクエストが完了した後。その後、接続を閉じ、新しい接続を開きます。HTTP 1.0 キープアライブ機能を正しく実装したと確信しています。私の質問は次のとおりです。最初のリクエストが完了した後、curlは接続を介して何を期待していますか? 接続が切れていると判断するのはなぜですか？
PS 上記のコードはhttp://www.paulgriffiths.net/program/c/webserv.phpから改作されました