Search results

That doesn't seem to be happening. I stop the external (FastCGI in this case) application, and it falls straight back to the built-in 404.

Hi there, If you have a 404 error page that is set to an external server, and the external server is down, when you go to an invalid URL you get the internal/default 404 message, rather than the page configured as the 503 Gateway Not Connected message.

one more thing... errors that happen inside the OpenSSL libraries seem to give me this sort of thing: 2004-07-30 15:49:17.178 [DEBUG] Created new Listener [*:7080]. 2004-07-30 15:49:17.178 [DEBUG] Created new Listener [*:80]. 2004-07-30 15:49:17.178 [DEBUG] Created new Listener...

No header at all! I used `tcpflow' to capture the output and discovered this (tcpflow really is the bomb for debugging problems like this :-)). Yes, Apache should be making sure it is complying with the HTTP protocol, given that it is (supposedly) an HTTP server, not just a remote buffer...

I want it longer on my development LSWS! :-)

If you rename a virtual host via the PHP admin interface, the listener configurations are not automatically updated. LSWS 1.5.5.

Hi there, Replacing our legacy Apache applications with LSWS 1.5.5 has been mostly successful, however; The "Proxy" external application mode does not seem to work, unless the buffering option is set to "Yes" The "Proxy" mode does not exhibit Apache-style tolerance of responses from...

2004-07-27 17:41:50.185 [ERROR] [SSL] Config SSL Context for listener 210.54.92.188:443 with Certificate File: /mv/ ssl/www.bnz.marketview.co.nz.reply and Key File:/mv/ssl/www.bnz.marketview.co.nz get SSL error: error:0906D066:PEM routines:PEM_read_bio:bad end line I've just stuck my SSL...

Excellent! Here's a test program. Fantastic, it works as expected. For closure of the topic, here is my test program, which works well on my Perl 5.8.4 platform (FCGI module version = 0.67) #!/usr/bin/perl # Copyright (c) 2004, Sam Vilain. This program is free software; you may #...

Indeed. Which is why if you were to implement it, you'd only employ it in situations where the buffer would otherwise sit there and stagnate. Normal behaviour - serving files, and flushing responses once they have been completely received would proceed as normal.

Yes, there are lots of good reasons to buffer. An alternative to going down the nph vs normal mode might be to simply use Nagle's algorithm (flush output buffer if it is full, or if there was N ms of inactivity). This is of course really simple to implement in userspace threaded / event...

Thanks for your response. As detailed in http://www.fastcgi.com/devkit/doc/fcgi-spec.html#S5.5, FCGI_END_REQUEST should only be used at the end of the response. As the response consists of multiple parts (with a second or two delay between each one), there is only one logical request to the...

Hi, I'm trying to use LiteSpeed to generate x-mixed-replace content via a FastCGI responder. Using `strace(1)', I can see that my application is sending the response to LSWS and flushing completely. However, LSWS is not flushing the response to the client as the individual parts are...