Hi All,

This is not necessarily a XOOPS question but more related to Apache, IIS and mod_proxy.

We have the following installed on the same machine:
Apache 2.2.4, PHP 4.4.4, MySQL 4.17, IIS6

We have a proxy set up for different instances of XOOPS in sub-folders.

http://www.mysite.com/xoops1/
http://www.mysite.com/xoops2/

I believe there is a bug in mod_proxy.

When the folder xoopsXX is set as a proxy to IIS running on a different port the the URLhttp://www.mysite.com/xoopsXX./ shows the list of files in the folder and does not proxy to IIS as I expect.

Can anyone help or reply with what I should look for to get a fix?

Thanks for any help!

Why in the world would you use Apache to proxy to IIS?! That's like using your best cookware to make dinner then serving it in on paper plates. If you're going to be running .NET on your site, then I can see needing IIS, but even standard ASP will run on Apache.

But I digress...

Did you read Apache's mod_proxy documentation?

As blasphamous as the idea is to me, seems you're not the only one who has done it, so you might find the following Google Search helpful.

Sorry I don't have a direct answer for you, but what you are doing is a little unusual. Hope the pointers get you going in the right direction.

Yeah, yeah, yeah... I know.. I know! Apache rules!

After I started in my current position, I inherited several classic ASP and .NET applications! The philosophy of the group is don't fix what ain't broke. So I'm stuck.

I have moved several of the apps to XOOPS modules and will work on the others as time permits, but projects that earn money always get in the way.. :)


You say, "unusual" - I say this is my "normal!" :)

Thanks for the information.. I'll keep digging.

A <location> directive might solve my problem...

<LocationMatch "/[fF][oO][lL][dD][eE][rR][\.]*/*\w+$">
Options -Indexes
ErrorDocument 403 /error/?num=403
</LocationMatch>
ProxyPass /support/http://thesite.com:1080/folder/
ProxyPassReverse /support/http://thesite.com:1080/support/

I'll post if we ever get it working...*/

Just givin' ya a hard time.

I just left a decidedly M$ shop in January, so I know all to well what you are saying. At least the people you are working with are open to new ideas. The company I was working for wouldn't touch it unless it had M$ all over it.

Good luck man! Let us know how it turns out.

We found a simple solution (maybe) ...

We added an index.php file in the top level folder that simple redirects to a URL with ending with default.asp. As Microsoft junkies know, default.asp is typically the file IIS sees as it's "DirectoryIndex."

As long as we have all of the folders with the appropriate index.php file at the top level, we are good to go.

My next step is to write a script to traverse our webroot tree and check for the existence of the index.php file.

Hey - it works!!!

Enjoy...