Apache, iPlanet CGI question

[jmiturbe]

Hello,

We have been doing "jumps" between different iPlanet web servers (on different DMZs) using a weblogic proxy lib. At the first level, only static contents are served, and "dinamic" content like CGIs are executed on the second level and served to the first level through the mentioned library.

Now we have installed a linux server with apache 1.3.27 on the second DMZ (second level). This way the users access an iPlanet web server, and when the execution of a CGI is needed the jump must be done to the Apache using the proxy lib.

It works well between iPlanets with all kind of CGIs but when the second server is an Apache it does not work properly with C CGIs or with shell-script CGIs. It does work with perl CGIs.

Does anybody know what is happening? Any ideas on how to solve it?

Excuse my poor english and my low web knowledge. If you need more info just ask for it.

Thanks in advance,

jmiturbe

 

[cdeardor]

Are there any entries in your access or error logs on the apache server showing what the cgi-programs you're trying to execute are doing? If it's C programs and shellscript progrmas, make sure your environment is setup correctly and that with the shellscripts you're fully qualifying all commands "e.g. /opt/apache2/bin/httpd". Also, have you tried running the cgi's directly on the tier 2 machine rather than going through the iplanet servers first?

 

[jmiturbe]

Hello again,

The CGIs run perfectly without using the first iPlanet (accesing them from the Apache directly). The problem comes only when using iPlanet as the front-end webserver (serves static contents and performs the jump for CGIs through proxylib) and apache as the backend webserver (executes the CGIs).

We had some luck and used a browser configured for HTTP 1.0 to access the system. We saw that it worked!!!

Inittially we didn't know why this worked only with this browser, but when we understood what was happening, we forced apache web server to reply with HTTP 1.0 (BrowserMatch,downgrade-1.0 and force-response-1.0). Things seem to work this way.

But we already want to get this work under HTTP 1.1 protocol , to eliminate any kind of unwanted dependencies, possible compatibility problems, ...

Does anybody know why can this work under HTTP 1.0 and not under HTTP 1.1, and how to fix this issue?

Thanks in advance,

jmiturbe