RE: Envariables for logging phase only
Rodent of Unusual Size wrote: Joshua Slive wrote: LogStatus envname[=val] statusre ... (I think the envname should be last to align with SetEnvIf.) I didn't do it that way so that multiple status codes could be specified, a la AddType and friends. But if the first argument is a regex, then switching them so the envariables are last, like SetEnvIf, is better. Still, i think if we could make this named right it'd be better although, i am tending towards prefering a module for this; like, mod_log_on_steroids or something... -- James
Re: Directory index and Mulitviews problem - 2.0.39
Greg Ames wrote: Robert Simonson wrote: We've been testing with 2.0.39, and we've run into a strange problem when negotiating for a directory index page. I haven't figured out how to reproduce this...I get myhtml.index. ooops, I should have mentioned that I was using current cvs HEAD. Have you tried this? Greg
Removing modules
On Fri, Jul 26, 2002 at 01:52:03PM -0600, Brad Nicholes wrote: +1, personally I would like to see it added back to the Apache modules. I'm not sure why it was removed. Maybe somebody could shed some light on that. mod_auth_ldap has been like mod_proxy - in, out, in, out. I wouldn't mind seeing it folded back in. But, I know that a lot of people were against it last time. I think we may need to come up with a more coherent policy for the unbundled modules in the HTTP Server project. (I don't know if the PMC wants to discuss this or not.) In the past, people have suggested a CPAN/PEAR-approach where modules are downloaded when needed. This way we could reduce the stock distribution to the bare bones. We would also have to rethink our configuration policy (almost to make it like Perl does - interactive). -- justin
mod_proxy drops the content-length header
In case anyone is interested, here are some captures taken with Sniffer Pro. The key things to note are that Apache 2.0.39 mod_proxy drops the Content-Length header, and also that it inserts Content-Type: text/plain. This behaviour is causing Web-Polygraph to report superfluous errors. Graham Wiseman [EMAIL PROTECTED] FSC Internet Corp. ** Original request from client: HTTP: Line 1: GET /w06df39e0.4a3e422c:0006/t04/_000e HTTP/1.0 HTTP: Line 2: Accept: */* HTTP: Line 3: Host: target1.lab.fscinternet.com:80 HTTP: Line 4: X-Xact: 06df39e0.4a3e422c:0002 06df39e0.4a3e422c:00b2 HTTP: Line 5: X-Loc-World: 06df39e0.4a3e422c:0006 -1/14 7 HTTP: Line 6: X-Rem-World: 06df39e0.4a3e422c:0006 -1/14 7 HTTP: Line 7: X-Target: 10.249.1.50:80 HTTP: Line 8: X-Abort: 1433599079 1880685060 HTTP: Line 9: X-Phase-Sync-Pos: 0 HTTP: Line 10: Connection: keep-alive ** Proxied request from Apache 2.0.39 mod_proxy: HTTP: Line 1: GET /w06df39e0.4a3e422c:0006/t04/_000e HTTP/1.1 HTTP: Line 2: Host: target1.lab.fscinternet.com HTTP: Line 3: Accept: */* HTTP: Line 4: X-Xact: 06df39e0.4a3e422c:0002 06df39e0.4a3e422c:00b2 HTTP: Line 5: X-Loc-World: 06df39e0.4a3e422c:0006 -1/14 7 HTTP: Line 6: X-Rem-World: 06df39e0.4a3e422c:0006 -1/14 7 HTTP: Line 7: X-Target: 10.249.1.50:80 HTTP: Line 8: X-Abort: 1433599079 1880685060 HTTP: Line 9: X-Phase-Sync-Pos: 0 HTTP: Line 10: Max-Forwards: 10 HTTP: Line 11: X-Forwarded-For: 10.101.0.6 HTTP: Line 12: X-Forwarded-Host: target1.lab.fscinternet.com:80 HTTP: Line 13: X-Forwarded-Server: target1.lab.fscinternet.com ** Response from server: HTTP: Line 1: HTTP/1.0 200 OK HTTP: Line 2: Cache-Control: public HTTP: Line 3: Date: Thu, 25 Jul 2002 23:05:23 GMT HTTP: Line 4: Connection: keep-alive HTTP: Line 5: Expires: Sun, 15 Dec 2002 19:26:25 GMT HTTP: Line 6: Last-Modified: Tue, 18 Jun 2002 11:11:47 GMT HTTP: Line 7: Content-Length: 34879 HTTP: Line 8: X-Target: 10.249.1.50:80 HTTP: Line 9: X-Xact: 06df39d3.7dbd4c7b:0002 06df39e0.4a3e422c:7f4d HTTP: Line 10: X-Abort: 1501744696 447802481 HTTP: Line 11: X-Phase-Sync-Pos: 0 ** Proxied response from Apache 2.0.39 mod_proxy: HTTP: Line 1: HTTP/1.1 200 OK HTTP: Line 2: Date: Thu, 25 Jul 2002 23:05:23 GMT HTTP: Line 3: Server: Apache HTTP: Line 4: Cache-Control: public HTTP: Line 5: Expires: Sun, 15 Dec 2002 19:26:25 GMT HTTP: Line 6: Last-Modified: Tue, 18 Jun 2002 11:11:47 GMT HTTP: Line 7: X-Target: 10.249.1.50:80 HTTP: Line 8: X-Xact: 06df39d3.7dbd4c7b:0002 06df39e0.4a3e422c:7f4d HTTP: Line 9: X-Abort: 1501744696 447802481 HTTP: Line 10: X-Phase-Sync-Pos: 0 HTTP: Line 11: Connection: close HTTP: Line 12: Content-Type: text/plain
Re: daedalus is running httpd-2.0.pre40
Ryan Bloom wrote: Stop handwaving. No-one is suggesting overwriting httpd.conf. Re-read that paragraph. In no place did I say we were. I said we were re-installing the default config files on an upgrade Sorry if I misunderstood you, but I took 'default config files' to mean httpd.conf. If that's not what you meant, as it obviously wasn't, then my remarks don't apply. I'm -0 on the -*.conf files going into /conf/, so I guess we're in agreement on that, but I'm absolutely -1 on them not being supplied *somewhere*. -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ Millennium hand and shrimp!
Re: Envariables for logging phase only
At 10:21 AM 7/22/2002, Rodent of Unusual Size wrote: Obviously this can be done with piped logging, but I consider that a bit of a handwave. It appears that here really isn't any simple way to accomplish what seems to actually be a reasonable thing. It can be worked around with ErrorDocument and mod_rewrite, I think, but that too is a bag on the side. So, unless someone has a solution I'm missing, I'd like to propose adding a sort of pseudo-envariable during the logging phase. Something like 'status_is_NNN', where NNN is appropriately substituted. Then something like CustomLog logs/access_log combined env=!status_is_404 Wouldn't it make more sense to bite the bullet, skip the extra envvar creation, and finally add status as an alternative, where we provide env? I'd rather we err on the side of feature richness, then to start proliferating more envvars that must be set up on every request [even when they aren't used.] Bill
