Bug 76450
Summary: | .htaccess protected documents produce "The document contains no data." errors. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Carl T. Miller <carl> |
Component: | httpd | Assignee: | Joe Orton <jorton> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-01-25 16:47:11 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Carl T. Miller
2002-10-21 23:01:03 UTC
After verifying that this does work correctly on another server, I reinstalled the OS, and now it works correctly. I'll take it back. I still have a problem on my web server. I reinstalled everything again, and I'm seeing the exact same results as described above. What I find interesting is that if I deny/allow by IP address and try to open from an allowed address, it works. If I try to open from a denied addess, I get the "Document contains no data" message. I'm starting to wonder if this has anything to do with specific hardware. The server has dual Pentium IIs, and I'm running the latest i686 kernel from Red Hat. Let me know if I can send you anything that could help you troubleshoot this. I could never reproduce this; can you attach your httpd.conf and error_log? What was the specific path to the .htaccess file you used? Thanks for the report. This is a mass bug update; since this release of Red Hat Linux is no longer supported, please either: a) try and reproduce the bug with a supported version of Red Hat Enterprise Linux or Fedora Core, and re-open this bug as appropriate after changing the Product field, or, b) if relevant, try and reproduce this bug using the current version of the upstream package, and report the bug upstream. c) report the bug to the Fedora Legacy project who may wish to continue maintenance of this package. |