Bug 2175717

Summary: 'Test Connection' button in 'New HTTP Proxy' returns success with invalid URL
Product: Red Hat Satellite Reporter: Matyas Strelec <mstrelec>
Component: HTTP ProxyAssignee: Chris Roberts <chrobert>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.13.0CC: ahumbe, chrobert, ehelms, iballou, jpathan
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: https://projects.theforeman.org/issues/36919
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 16:10:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Success alert even with invalid URL none

Description Matyas Strelec 2023-03-06 12:32:04 UTC 
Created attachment 1948329 [details]
Success alert even with invalid URL

Created attachment 1948329 [details]
Success alert even with invalid URL

Description of problem:
When creating new HTTP Proxy, the `Test Connection` returns a `Success alert:HTTP Proxy connection successful.`, even when the URL entered is invalid.

Version-Release number of selected component (if applicable):
Satellite 6.13.0 Snap 13

How reproducible:
Always

Steps to Reproduce:
1. Go to Satellite -> Infrastructure -> HTTP Proxies
2. New HTTP Proxy
3. Enter an invalid URL in URL field
4. Click `Test Connection`

Actual results:
`Success alert:HTTP Proxy connection successful.` returned always even with invalid URL.

Expected results:
Success alert only for valid URLs, error alert for invalid URLs.

Additional info:
Comment 2 Eric Helms 2024-06-06 16:10:21 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.