Bug 90546
Summary: | Error Document 400 does not return properly for requests which violate the RFC. | ||
---|---|---|---|
Product: | [Retired] Stronghold for Red Hat Linux | Reporter: | Jp Robinson <robinson> |
Component: | stronghold-apache | Assignee: | Joe Orton <jorton> |
Status: | CLOSED WONTFIX | QA Contact: | Stronghold Engineering List <stronghold-eng-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | stronghold-eng-list, tao |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-05-25 13:08:34 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
Jp Robinson
2003-05-09 15:38:32 UTC
Is this a practical problem for some customer? I'm surprised if there are any clients out there which issue these broken requests. It concerned a customer who was running various security tests, including a test for HTTP TRACE which did requests similar to above. The custom error messages not showing were of concern, as this may give away information about the software being run. While I concede the fact I know of no actual "client" that will produce such bad requests, I can see the customer's point regarding the error message. Given that this isn't a practical issue, no intention to fix at this time. |