---
name: "Plack::Middleware::LighttpdScriptNameFix"
section: "3pm"
platform: "linux"
package: "libplack-perl"
version: "1.0051-1"
release: "Debian 13 (Trixie)"
platforms: ["linux"]
url: "https://new.carta.tech/Plack::Middleware::LighttpdScriptNameFix"
---

# Plack::Middleware::LighttpdScriptNameFix(3pm)

fixes wrong SCRIPT\_NAME and PATH\_INFO that lighttpd sets

## NAME

Plack::Middleware::LighttpdScriptNameFix - fixes wrong SCRIPT\_NAME and PATH\_INFO that lighttpd sets

## SYNOPSIS

```
  # in your app.psgi
  use Plack::Builder;
  builder {
    enable "LighttpdScriptNameFix";
    $app;
  };
  # Or from the command line
  plackup -s FCGI -e 'enable "LighttpdScriptNameFix"' /path/to/app.psgi
```

## DESCRIPTION

This middleware fixes wrong `"SCRIPT_NAME"` and `"PATH_INFO"` set by lighttpd when you mount your app under the root path ("/"). If you use lighttpd 1.4.23 or later you can instead enable `"fix-root-scriptname"` flag inside `"fastcgi.server"` instead of using this middleware.

## CONFIGURATION

- script\_name

  Even with `"fix-root-scriptname"`, lighttpd *still* sets weird `"SCRIPT_NAME"` and `"PATH_INFO"` if you mount your application at `""` or something that ends with `"/"`. Setting `"script_name"` option tells the middleware how to reconstruct the new correct `"SCRIPT_NAME"` and `"PATH_INFO"`.

  If you mount the app under `"/something/"`, you should set:

  ```
    enable "LighttpdScriptNameFix", script_name => "/something";
  ```

  and when a request for `"/something/a/b?param=1"` comes, `"SCRIPT_NAME"` becomes `"/something"` and `"PATH_INFO"` becomes `"/a/b"`.

  `"script_name"` option is set to empty by default, which means all the request path is set to `"PATH_INFO"` and it behaves like your fastcgi application is mounted in the root path.

## AUTHORS

Yury Zavarin

Tatsuhiko Miyagawa

## SEE ALSO

Plack::Handler::FCGI \<http://github.com/plack/Plack/issues#issue/68\> \<https://redmine.lighttpd.net/issues/729\>