The requested file was not found.
"; + header_len = strlen(response_header); + send(client_fd, response_header, header_len, 0); + close(client_fd); + count = count + 1; + continue; + } + + printf("File opened successfully\n"); + + response_header = "HTTP/1.1 200 OK\nContent-Type: text/plain\n\n"; + header_len = strlen(response_header); + send(client_fd, response_header, header_len, 0); + + total_sent = 0; + while (feof(file) == 0) { + line = fgets(file, 8192); + line_len = strlen(line); + if (line_len > 0) { + send(client_fd, line, line_len, 0); + total_sent = total_sent + line_len; + } + } + + printf("Sent %d bytes\n", total_sent); + + fclose(file); + close(client_fd); + printf("Connection closed\n\n"); + + count = count + 1; + } + + close(server_fd); + printf("Server shutdown after %d requests\n", count); + return 0; +} +``` + +#### Key Concepts + +**Socket Creation and Binding:** +The server creates a TCP socket, binds it to port 8080, and listens for incoming connections. + +**Request Loop:** +The server runs a loop accepting up to 100 connections. For each connection: +1. Accept the client connection +2. Receive the HTTP request +3. Open the requested file +4. Send HTTP response headers +5. Send file content line by line +6. Close the connection + +**Error Handling:** +The server checks for errors at each step and provides appropriate HTTP error responses (404 for file not found). + +**Buffer Usage:** +The `char buffer[4096]` declaration creates a receive buffer. In RC, char arrays are used for socket recv() operations but cannot be directly manipulated as strings. + +**File Streaming:** +Instead of loading the entire file into memory, the server reads and sends it line by line using `fgets()` and `send()`, which is more memory-efficient. + +#### Important Limitations + +**String Manipulation:** +RC's type system has limitations when working with char arrays. Functions like `substr()`, `strpos()`, and `strcmp()` work with string pointers (`char*`) but not with char arrays used as buffers. + +**Simplified HTTP Parsing:** +The example serves a fixed file rather than parsing the HTTP request path. Full HTTP request parsing requires string manipulation that is challenging with RC's buffer semantics. + +**Working with Buffers:** +- Use `char buffer[size]` for recv() operations +- Buffers receive data but cannot be easily parsed as strings +- Use `char *str = "..."` for string literals and manipulation +- Keep HTTP logic simple to avoid buffer parsing issues + +#### Testing the Server + +Run the server: +```bash +./bin/rc examples/http_fileserver.rc +``` + +Test with curl: +```bash +curl http://localhost:8080/ +``` + +Test with a browser: +``` +http://localhost:8080/ +``` + +#### Production Considerations + +For production HTTP servers: +1. Add request timeout handling +2. Implement proper HTTP request parsing (in a more suitable language) +3. Add support for multiple file types and MIME types +4. Implement connection pooling for better performance +5. Add logging for debugging and monitoring +6. Consider using async I/O for handling multiple concurrent connections + +This example demonstrates RC's capabilities for network programming while working within its type system constraints. + ## Comments RC supports single-line comments using `//`. diff --git a/examples/http_fileserver.rc b/examples/http_fileserver.rc index 7aa366a..ab8bae7 100644 --- a/examples/http_fileserver.rc +++ b/examples/http_fileserver.rc @@ -36,8 +36,8 @@ int main() { printf("Example: http://localhost:8080/\n\n"); filename = "README.md"; - count = 0; - while (count < 100) { + count = 1; + while (count > 0) { printf("Waiting for connection %d\n", count + 1); client_fd = accept(server_fd);