Project

General

Profile

Bug #1416

request the uri "/personal/" but get the index.jsp's source

Added by songday almost 12 years ago. Updated almost 11 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
mod_proxy
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Missing in 1.5.x:

Description

i am typing:


  $HTTP["url"] =~ ".jsp" {
    proxy.balance = "fair" 
    proxy.server = ( "" => 
      (( "host" => "127.0.0.1", 
         "port" => 8090 ),
       ( "host" => "127.0.0.1", 
         "port" => 8091 )) )
  }

or


  proxy.balance = "fair"[[BR]]
  proxy.server = ( ".jsp" => (
    ( "host" => "127.0.0.1", "port" => 8090 ),
    ( "host" => "127.0.0.1", "port" => 8091 ))
  )

then i request the "/personal/index.jsp" uri , IE display right page result

but when i request the "/personal/" instead of "/personal/index.jsp" , IE will display source code of /personal/index.jsp

my email address is :

History

#1

Updated by Anonymous almost 12 years ago

you can add .jsp to the static files exclusion

static-file.exclude-extensions = ( ".pl", ".fcgi", ".php" , ".jsp")

#2

Updated by Anonymous almost 12 years ago

the same thing happens with php source code if mod_proxy is used for an apache+php backend

#3

Updated by Anonymous almost 12 years ago

Replying to anonymous:

you can add .jsp to the static files exclusion

static-file.exclude-extensions = ( ".pl", ".fcgi", ".php" , ".jsp")

thanks for your reply, so i follow your teach to add ".jsp" in "static-file.exclude" line and restart lighttpd service

then I request the uri "/personal/", the lighttpd return 404 instead of index.jsp's source code, but why lighttpd can NOT return "/personal/index.jsp" automatic ?

#4

Updated by stbuehler over 11 years ago

mod_indexfile.c is triggered too late, and mod_proxy does the extension checking before that.

As a workaround you could use a rewrite rule "^/personal/?$" => "/personal/index.jsp".

#5

Updated by stbuehler about 11 years ago

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

mod_proxy triggers only on url, not on physical filenames; the same goes of course for the url conditional: it checks the url, not the filename.

mod_indexfile only changes the filename, not the url.

There is nothing wrong with that.

We won't change the behaviour of mod_proxy to also trigger on filenames in 1.4 (in 1.5 it should work with mod_proxy_core).

#6

Updated by stbuehler almost 11 years ago

  • Status changed from Fixed to Invalid

Also available in: Atom