RequestServer service

RequestServer is a dedicated service process that handles all network operations for Ladybird. Each WebContent process gets its own RequestServer instance to perform uploads and downloads on its behalf.

Overview

RequestServer provides network access to WebContent processes while maintaining security isolation. It handles:

HTTP and HTTPS requests
WebSocket connections
DNS resolution through LookupServer
HTTP disk caching
TLS/SSL certificate management
Resource substitution for testing

WebContent processes cannot directly access the network. All network operations must go through RequestServer for security.

Architecture

RequestServer acts as a proxy between WebContent and the network, implementing a client-server IPC model.

Key components

ConnectionFromClient

Manages IPC connections from WebContent processes. Handles multiple request types:

Standard HTTP/HTTPS requests
WebSocket connections
Cache operations
DNS configuration

class ConnectionFromClient : public IPC::ConnectionFromClient<
    RequestClientEndpoint, 
    RequestServerEndpoint
> {
    HashMap<u64, NonnullOwnPtr<Request>> m_active_requests;
    HashMap<u64, RefPtr<WebSocket::WebSocket>> m_websockets;
};

Located in Services/RequestServer/ConnectionFromClient.h:22

Request

Represents an individual HTTP request with:

Request method (GET, POST, etc.)
Headers and body
Response handling
Progress tracking

Located in Services/RequestServer/Request.h

Resolver

Handles DNS lookups by communicating with the system’s LookupServer service.

RequestServer asks LookupServer for DNS resolution rather than doing lookups directly.

CURL integration

RequestServer uses libcurl for HTTP operations:

Multi-handle for concurrent requests
Event-based I/O with notifiers
Custom callbacks for socket and timeout events

static int on_socket_callback(void*, int sockfd, int what, void* user_data, void*);
static int on_timeout_callback(void*, long timeout_ms, void* user_data);

Located in Services/RequestServer/ConnectionFromClient.h:70

Process spawning

RequestServer is spawned by WebContent when needed:

WebContent creates RequestServer on initialization
Communication occurs over IPC sockets
Multiple WebContent processes = multiple RequestServer processes

Each WebContent process maintains its own RequestServer instance for isolation.

HTTP disk cache

RequestServer supports optional disk caching for HTTP resources:

Cache modes

Mode	Description
`disabled`	No caching (default)
`enabled`	Standard HTTP cache behavior
`partitioned`	Cache partitioned by site for privacy
`testing`	Temporary cache for tests

Enable caching with the --http-disk-cache-mode flag:

RequestServer --http-disk-cache-mode=enabled

Cache operations

The cache supports:

Size estimation by access time
Bulk removal of cached entries
Respect for HTTP cache headers
Partitioning by origin for privacy

WebSocket support

RequestServer manages WebSocket connections through WebSocketImplCurl:

virtual void websocket_connect(
    u64 websocket_id, 
    URL::URL, 
    ByteString origin,
    Vector<ByteString> protocols,
    Vector<ByteString> extensions,
    Vector<HTTP::Header>
) override;

Features:

Full duplex communication
Binary and text frames
Connection management
TLS support for secure WebSockets (wss://)

Located in Services/RequestServer/ConnectionFromClient.h:65

Resource substitution

For testing, RequestServer can substitute local files for network resources:

class ResourceSubstitutionMap {
    static ErrorOr<OwnPtr<ResourceSubstitutionMap>> load_from_file(StringView path);
};

Use with --resource-map flag:

RequestServer --resource-map=/path/to/substitutions.json

Resource substitution is useful for offline testing and avoiding external dependencies in test suites.

Security features

Sandboxing

RequestServer runs with limited privileges:

Separate unprivileged user
Restricted system calls via pledge()
Limited filesystem access via unveil()
Cannot spawn other processes

Certificate management

Supports custom TLS certificates:

RequestServer --certificate=/path/to/cert.pem

Certificates can be set per-request or globally.

Configuration options

Option	Description
`--certificate`	Path to TLS certificate file
`--http-disk-cache-mode`	Cache mode (disabled, enabled, partitioned, testing)
`--resource-map`	JSON file mapping URLs to local files
`--wait-for-debugger`	Pause on startup for debugger attachment
`--mach-server-name`	Mach server name (macOS only)

Request pipeline

Receive request: WebContent sends request via IPC
DNS resolution: Resolve hostname through LookupServer
Connection: Establish TCP/TLS connection
Send request: Transmit HTTP request with headers and body
Receive response: Stream response data back to WebContent
Cache: Optionally store in disk cache

Proxy support

RequestServer respects proxy configuration:

virtual void start_request(
    u64 request_id,
    ByteString method,
    URL::URL,
    Vector<HTTP::Header>,
    ByteBuffer body,
    HTTP::CacheMode,
    HTTP::Cookie::IncludeCredentials,
    Core::ProxyData proxy_data  // Proxy configuration
) override;

Cookies are managed by WebContent, but RequestServer:

Includes cookies in requests as directed
Reports received cookies back to WebContent
Respects cookie security policies

Request revalidation

Supports HTTP cache revalidation:

void start_revalidation_request(
    Badge<Request>,
    ByteString method,
    URL::URL,
    NonnullRefPtr<HTTP::HeaderList> request_headers,
    ByteBuffer request_body,
    HTTP::Cookie::IncludeCredentials,
    Core::ProxyData proxy_data
);

Located in Services/RequestServer/ConnectionFromClient.h:40

Connection pooling

CURL handles connection reuse automatically:

Keep-alive connections
HTTP/2 multiplexing
Connection limits per host

Error handling

RequestServer reports various error conditions:

Network timeouts
Connection failures
DNS resolution errors
TLS certificate errors
HTTP protocol errors

Performance considerations

Concurrent requests: Multiple requests handled simultaneously
Async I/O: Non-blocking event-driven architecture
Connection reuse: HTTP keep-alive and HTTP/2
Disk cache: Reduces redundant network fetches

WebContent: Primary client of RequestServer
LookupServer: Global DNS resolution service
Browser: Spawns WebContent which spawns RequestServer

Services

Utilities

Editor Configuration

Overview

Architecture

Key components

ConnectionFromClient

Request

Resolver

CURL integration

Process spawning

HTTP disk cache

Cache modes

Cache operations

WebSocket support

Resource substitution

Security features

Sandboxing

Certificate management

Configuration options

Request pipeline

Proxy support

Request revalidation

Connection pooling

Error handling

Performance considerations

Build docs developers (and LLMs) love

Services

Utilities

Editor Configuration

​Overview

​Architecture

​Key components

​ConnectionFromClient

​Request

​Resolver

​CURL integration

​Process spawning

​HTTP disk cache

​Cache modes

​Cache operations

​WebSocket support

​Resource substitution

​Security features

​Sandboxing

​Certificate management

​Configuration options

​Request pipeline

​Proxy support

​Cookie handling

​Request revalidation

​Connection pooling

​Error handling

​Performance considerations

​Related services

Build docs developers (and LLMs) love

Overview

Architecture

Key components

ConnectionFromClient

Request

Resolver

CURL integration

Process spawning

HTTP disk cache

Cache modes

Cache operations

WebSocket support

Resource substitution

Security features

Sandboxing

Certificate management

Configuration options

Request pipeline

Proxy support

Cookie handling

Request revalidation

Connection pooling

Error handling

Performance considerations

Related services