Web Request Path on PMSS
On a Pulsed Media seedbox or storage box, every web request passes through two servers: a shared nginx front door, then the lighttpd instance that belongs to your account. The same file in ~/www/public/ reaches your lighttpd under two different paths, depending on the address the visitor used, and nginx allows each visitor address 8 simultaneous connections to it. This page lists both, because custom lighttpd rules, reverse-proxy fragments and download behavior depend on them.
The chain
Visitors connect to nginx on ports 80 and 443 of the server. nginx forwards each request over the loopback interface to the lighttpd of the account that owns the path or hostname, on that account's own local port. lighttpd then serves a file from your home directory, hands a .php file to php-cgi over FastCGI, or proxies to an app of yours on another local port.
nginx only routes. Your own rules live in ~/.lighttpd/custom.d/ and apply inside lighttpd, after nginx has already rewritten the path. See Custom lighttpd Configuration for the directory and the worked examples.
Which path lighttpd receives
| Address a visitor uses | Path your lighttpd receives | Served from | Login |
|---|---|---|---|
https://SERVER/public-USERNAME/photo.jpg |
/photo.jpg (prefix removed) |
~/www/public/ |
none |
https://SERVER/~USERNAME/photo.jpg |
/photo.jpg (prefix removed) |
~/www/public/ |
none |
USERNAME.SERVER.pulsedmedia.com/photo.jpg, or your mcx.fi permalink |
/public-USERNAME/photo.jpg |
~/www/public/ |
none |
https://SERVER/user-USERNAME/app/ |
/user-USERNAME/app/ (unchanged) |
~/www/ |
panel login |
https://SERVER/webdav-USERNAME/ |
/webdav-USERNAME/ (unchanged) |
~/ |
panel login, WebDAV |
The two public path forms and the public hostnames reach the same files. They differ only in what nginx sends on: its forwarding address for the path forms ends in a slash, which removes the matched prefix, while the forwarding address for the hostnames carries /public-USERNAME/ itself. lighttpd maps both onto ~/www/public/. The /~USERNAME/ form exists so that the ~ never reaches lighttpd, whose default url.access-deny list refuses paths ending in ~ and .inc.
Consequences for your own rules
A $HTTP["url"] condition matches the path lighttpd received, not the address in the visitor's browser. A condition written as ^/app/ therefore applies to the two path forms only. Through the subdomain or permalink the same request arrives as /public-USERNAME/app/, the condition does not match, and a reverse-proxy fragment inside it is skipped. lighttpd then looks for a file called app/ and answers 404.
A rule that has to hold on every address takes the prefix as optional:
$HTTP["url"] =~ "^(/public-USERNAME)?/app/" {
setenv.add-response-header = ( "X-Robots-Tag" => "noindex" )
}
To see which path a request arrived as, follow the access log while loading the URL:
tail -f ~/.lighttpd/access.log
The request line in each entry is the path lighttpd received. This applies to every condition on the URL.
Limits at the nginx layer
nginx applies a transfer limit and a connection limit to each address form. The values below are read from the PMSS nginx templates; in nginx notation k and m are KiB and MiB.
| Address form | Rate applies after | Rate per connection | Simultaneous connections per client address |
|---|---|---|---|
public path, /~USERNAME/, subdomain, permalink |
first 100 MiB of a response | 32 768 KiB/s (32 MiB/s, about 268 Mbit/s) | 8 |
/user-USERNAME/ |
first 1 024 MiB of a response | 102 400 KiB/s (100 MiB/s, about 839 Mbit/s) | 16 |
/webdav-USERNAME/ |
first 100 MiB of a response | 102 400 KiB/s | 16 |
The rate limit applies to each connection and starts only after the stated amount of one response has been sent, so a small page is never slowed. The connection limit counts open connections per visitor IP address in one nginx zone (addr); a visitor above the limit is refused by nginx before lighttpd sees the request. nginx's default refusal status for this is 503 (nginx limit_conn module); PMSS does not change it for these paths.
Two further nginx settings shape long requests. nginx waits up to 300 seconds (600 on /webdav-USERNAME/) between two reads from lighttpd and between two writes to the visitor, and it does not buffer proxied responses, so a response streams to the visitor as lighttpd produces it.
lighttpd itself adds no throttle. The generated config carries connection.kbytes-per-second and server.kbytes-per-second, and PMSS rewrites any value above 65 535 to 0 when it renders your config, which switches the lighttpd limit off. The nginx limits above are the ones that apply.
PHP workers
.php files run in php-cgi processes started by lighttpd. PMSS sizes the pool from the account's CPU quota: about 4 worker threads per 100 % of quota, rounded up to whole groups of 6, so between 6 and 48 threads. PHP's memory_limit is set between 125 MiB and 1 024 MiB. A worker is recycled after 5 000 requests. Your own PHP settings go in ~/.lighttpd/php.ini; PMSS manages a few lines in that file, memory_limit among them.
The index file order is index.php, index.html, index.lighttpd.html.
What an app receives
Every proxied request reaches your lighttpd from nginx on the loopback interface, so the connection address is local. nginx sets Host, X-Real-IP, X-Forwarded-For, X-Forwarded-Proto and Forwarded; an app that needs the visitor's address or the original scheme reads those. nginx also passes the Authorization header on, and lighttpd passes it to a backend you proxy to unless a fragment removes it; the fragment form that removes it is on Lighttpd Custom Configuration.
Where the values come from
The numbers on this page are read from the public PMSS source at release 2026-10-21: etc/seedbox/config/template.nginx-user and scripts/lib/nginxConfig/templates.php for the nginx locations and limits, etc/seedbox/config/template.nginx-proxy_params for the headers and timeouts, etc/seedbox/config/template.lighttpd and scripts/lib/lighttpd/configRender.php for the lighttpd config, and scripts/util/userConfigLighttpd.php for the PHP clamps. Limits are PMSS defaults and can change in a later release; the access log shows what a given request did.
Every Seedbox and Storage Box runs this stack with no setup; Web Hosting on PMSS lists what to put on it.
See also
- Web Hosting on PMSS — the public web folder and what can be hosted on it
- Custom lighttpd Configuration — where your rules go and worked examples
- Lighttpd Custom Configuration — proxy fragments, the Authorization header and the app guides
- Custom Domains on PMSS — putting your own domain in front of the public folder
- Permalinks on PMSS — the mcx.fi hostname that serves the public folder