404 error behind a lighttpd mod_proxy

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install siab 2.10 from deb pkg, letting default settings
2. Setup a reverse-proxy with lighttpd to access siab from 
https://example.com/terminal/
3. Go to https://example.com/terminal/
-> Error 404.

See attached the log of siab while it give me that 404 error :

The lighttpd conf piece looks like : 

--------------------------------------------------------------
    $HTTP["host"] =~ "example.com" {
        proxy.server = ( "/terminal/" =>
                    (
                     ( "host" => "127.0.0.1", "port" => 4200)
                    )
                    )
    }
--------------------------------------------------------------

P.S: It works flawlessly if I access it directly towards the 4200 port.

Original issue reported on code.google.com by flyingpe...@gmail.com on 24 Dec 2009 at 2:26

Attachments:

• siab.log

[GoogleCodeExporter]

This is a problem with Lighttpd. As far as I can tell, it cannot actually be 
used to 
implement a real reverse proxy. Other web servers are a little more powerful.

As a work-around, you can configure ShellInABox to expect requests for 
"/terminal" 
instead of "/":

 --service '/terminal:LOGIN'

You won't need to do this, if you have a reverse proxy that correctly rewrites 
URLs 
on incoming requests.

Original comment by zod...@gmail.com on 24 Dec 2009 at 2:31

• Changed state: Invalid
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Ok, usefull workaround, thanks !
You gave me the answer to life the universe and everything ;-).

Original comment by flyingpe...@gmail.com on 24 Dec 2009 at 2:26

• Added labels: ****
• Removed labels: ****