Project

General

Profile

Actions

Bug #448

closed

SCRIPT_FILENAME and SCRIPT_NAME are wrong for [F]CGI scripts with full paths invoked as a directory index

Added by Anonymous over 15 years ago. Updated over 5 years ago.

Status:
Fixed
Priority:
Normal
Category:
mod_fastcgi
Target version:
ASK QUESTIONS IN Forums:

Description

A request to /~username/files/, where files is a directory, on lighttpd configured with:

server.indexfiles = (
"index.html",
"/global-site-overlay/ambindextrous/indexer"
)

fastcgi.server = (
"/fcgi-bin/ambindextrous/indexer" => (
"localhost" => (
"socket" => "/var/run/lighttpd/ambindextrous.sock",
"bin-path" => "/home/sites/fcgi-bin/ambindextrous/indexer"
)
)
)

Yields this in the FastCGI Request environment

"SCRIPT_NAME"=>"/~username/files//fcgi-bin/ambindextrous/indexer"
"REQUEST_URI"=>"/~username/files/",
"DOCUMENT_ROOT"=>"/home/services/lighttpd/html/" "SCRIPT_FILENAME"=>"/home/services/lighttpd/html//fcgi-bin/ambindextrous/indexer"

Instead of:

"SCRIPT_NAME"=>"/fcgi-bin/ambindextrous/indexer"
"REQUEST_URI"=>"/~username/files/",
"DOCUMENT_ROOT"=>"/home/services/lighttpd/html/" "SCRIPT_FILENAME"=>"/home/sites/fcgi-bin/ambindextrous/indexer"

-- aredridel


Related issues

Related to Feature #892: No PATH_INFO/PATH_TRANSLATED when using FastCGI as an index generatorFixedActions
Actions #1

Updated by gstrauss over 5 years ago

  • Related to Feature #892: No PATH_INFO/PATH_TRANSLATED when using FastCGI as an index generator added
Actions #2

Updated by gstrauss over 5 years ago

  • Description updated (diff)
  • Status changed from New to Patch Pending
  • Target version set to 1.4.40
Actions #3

Updated by gstrauss over 5 years ago

  • Status changed from Patch Pending to Fixed
  • Assignee deleted (jan)
Actions

Also available in: Atom