| Summary: | net-www/apache-2.0.58-r2 virtual host recursion loop (2.0.59-r2 is fine) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Whit Blauvelt <whit> |
| Component: | Current packages | Assignee: | Apache Team - Bugzilla Reports <apache-bugs> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Whit Blauvelt
2007-07-29 18:40:01 UTC
(In reply to comment #0) > Testing a basic virtual hosts setup in 2.0.58-r2 got a loop which LogLevel > debug shows as: > > [Sun Jul 29 13:41:33 2007] [debug] core.c(2757): [client 12.34.56.78] r->uri = > / > [Sun Jul 29 13:41:33 2007] [debug] core.c(2770): [client 12.34.56.78] > subrequested from r->uri = / > ... [repeats up to LimitInternalRecursion setting - then repeats again, > resulting in a huge log and 99% CPU usage] > > Simply upgrading to 2.0.59-r2 gave the correct response in this case: > > [Sun Jul 29 14:12:42 2007] [error] [client 12.34.56.78] Directory index > forbidden by rule: /web/denton/dentontaylor/ > > The case was that the index file was .htm, and DirectoryIndex hadn't been set > for that yet. > > Reproducible: Always > > Steps to Reproduce: > Install apache 2.0.58-r2, set up a virtual host (possibly without an index file > in the home directory), visit with browser. > > Actual Results: > System resources sucked up, huge log file generated quickly, apache2 must be > stopped. > > Expected Results: > The client browser should just have been sent an error message. > > Since 2.0.59-r2 does not have this problem, the suggested solution is to unmask > that soon, rather than leave 2.0.58-r2 as the latest apache (if not ~86). Could you please try 2.2.4-r10 ? That's the latest apache which is going to be stabled sooner or later (sooner I hope). > Could you please try 2.2.4-r10 ? That's the latest apache which is going to be
> stabled sooner or later (sooner I hope).
Can't try it at the moment on the box in question because it regards 1.3.* as a blocker. So after I get the sites on that box happy with 2.0.* I'll go to 2.2.*, but can't get 1.3.* out of the way for 2.2.* before then.
(Is 2.2.* truly incompatible with 1.3.*? Since Gentoo has end-of-lifed 1.*, others in my position will be better of if going to 2.2 without killing 1.3 is possible. 1.3.* and 2.0.* are perfectly happy running together.)
please reopen if this is still an issue with apache 2.2 |
