Project

General

Profile

Actions
Copy link

Bug #80

closed

mod_proxy + indexfiles == bug

Added by Anonymous over 19 years ago. Updated 7 months ago.

Status:
Invalid
Priority:
Low
Category:
mod_indexfile
Target version:
-
ASK QUESTIONS IN Forums:
No

Description

I have
server.indexfiles = { "index.rpy", .... }
and
proxy.server = ( ".rpy" => ...

If I type http://myhost/foobar/
and I have index.rpy in foobar it isn't proye'd, it's managed by lighttpd instead...
It should be exactly the same as if the user type http://myhost/foobar/index.rpy

-- fab

Actions
Copy link
 #1

Updated by Anonymous over 17 years ago

same goes with .php :/

Actions
Copy link
 #2

Updated by Anonymous over 17 years ago

Same error in 1.5.x svn 1811 too

-- boom

Actions
Copy link
 #3

Updated by stbuehler almost 16 years ago

  • Status changed from New to Fixed
  • Resolution set to wontfix

Proxy does not handle physical files, only urls. use mod_rewrite instead of indexfiles, or trigger proxy on something else.

Actions
Copy link
 #4

Updated by stbuehler almost 16 years ago

  • Status changed from Fixed to Wontfix
Actions
Copy link
 #5

Updated by gstrauss 7 months ago

  • Description updated (diff)
  • Category changed from core to mod_indexfile
  • Status changed from Wontfix to Invalid
  • Priority changed from High to Low
  • ASK QUESTIONS IN Forums set to No

One proper solution:
Rewrite requests to directories (ending in /) to .../index.rpy
url.rewrite = ("/$" => "$0index.rpy")
and then keep
proxy.server = ( ".rpy" => ... )

It should be exactly the same as if the user type http://myhost/foobar/index.rpy

No. After modules such as mod_proxy have had a chance to decide whether or not to handle the request, if mod_indexfile tries to handle the request in the filesystem, mod_indexfile checks the filesystem for files configured in index-file.names

Actions
Copy link

Also available in: Atom