Bug 561251

Summary: Apache: Error message should be thrown if http url is provided against the error type 401
Product: [Other] RHQ Project Reporter: Sunil Kondkar <skondkar>
Component: ConfigurationAssignee: Filip Drabek <fdrabek>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 1.4CC: sdharane
Target Milestone: ---Keywords: SubBug
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-26 09:20:23 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:
Bug Depends On:    
Bug Blocks: 565635, 577313    

Description Sunil Kondkar 2010-02-03 07:34:30 UTC 
Description of problem:
If user provides http url against the error type 401 in 'Document' field in 'Error Document' section, it is saved without any error message. A proper error message should be thrown as a full URL cannot be used in a 401 ErrorDocument directive.

Version-Release number of selected component (if applicable):
1.4.0-SNAPSHOT

How reproducible:


Steps to Reproduce:

1. Login to imanage UI.
2. Navigate to the apache httpd resource.
3. Navigate to the 'Configuration' tab of main server.
4. Click on 'Edit' button.
5. Click on 'Add New' button for 'Error Document' section.
6. Enter '401' in 'HTTP Response Code' field.
7.Enter the http url against the error type 401 in 'Document' field. (Ex: http://www.abc.com/pqr.html)
8.Click OK button.
9.Click 'Save' button.
  
Actual results:
If user provides http url against the error type 401 in 'Document' field in 'Error Document' section, it is saved without any error message.

Expected results:
A proper error message should be thrown as a full URL cannot be used in a 401 ErrorDocument directive.

Additional info:
Comment 1 wes hayutin 2010-02-16 16:58:04 UTC 
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug
Comment 2 wes hayutin 2010-02-16 17:02:59 UTC 
making sure we're not missing any bugs in rhq_triage
Comment 3 Charles Crouch 2010-04-23 12:52:54 UTC 
Filip
First thing to know is what are the valid values for the ErrorDocument and then consider if we can add validation to detect non-valid ones.
Comment 4 Sunil Kondkar 2010-04-26 09:20:23 UTC 
As per ErrorDocument directive - Apache can be configured to redirect to an external URL to handle the problem/error. So the test case needs to be updated.
Closing as this is not a bug.