In case you haven't already done this, maybe you could use wget (or something like wget) to get the exact output, including headers, etc.
--John Helmuth On 5/17/06, Chris Ridd <[EMAIL PROTECTED]> wrote:
On 17/5/06 8:06, dennis <[EMAIL PROTECTED]> wrote: > > I have a cgi we use to bind to a Sun ONE 5.2 LDAP Server to do > password reset. The CGI.pm based app dynamically creates a page > with an input textfield for the user's username (uid). Click > 'Search' and the script binds to LDAP, retrieves the user's > entry, and displays in a 2nd page. That 2nd page has the new > password fields. Click 'Reset' button, the script binds to > LDAP and modifies the password. Binds to the LDAP occur > in one routine; html output occurs only after the bind has > been terminated. > > The app works nicely in non-secure mode. It also successfully > runs in secure mode when run at the command line: the app > uses our ssl cert, binds to ldap, runs queries, and performs > password reset ok. > > The problem comes when trying to run as a cgi over port 636. > We get the dreaded server error. It appears to me that there's > some output emitted during the ldap bind that confuses > the web server. > > I've zipped a couple files that show cmd line output when > running reset.cgi with debug set to 0, then set to 1, which > I'll attach. > > Does anyone know a fix or workaround to this problem? It is hard to see what's going wrong, because it seems like the problem is only happening in the context of the web server, and your tests aren't being run in the same way. Almost certainly something in an underlying module's writing to stdout/stderr and confusing things. Using something like truss or strace on the web server might help you spot this. It will help debugging if the server's not being hit by any other queries at this point... Cheers, Chris
