This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2175717 - 'Test Connection' button in 'New HTTP Proxy' returns success with invalid URL
Summary: 'Test Connection' button in 'New HTTP Proxy' returns success with invalid URL
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: HTTP Proxy
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Chris Roberts
QA Contact: Satellite QE Team
URL: https://projects.theforeman.org/issue...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-06 12:32 UTC by Matyas Strelec
Modified: 2024-06-06 16:10 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 16:10:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Success alert even with invalid URL (71.75 KB, image/png)
2023-03-06 12:32 UTC, Matyas Strelec
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36919 0 Normal Ready For Testing Test Connection' button in 'New HTTP Proxy' returns success with invalid URL 2023-11-14 16:22:22 UTC
Github theforeman foreman pull 9903 0 None open Fixes #36919 - Add URL validation to HTTP Proxy URL field. 2023-11-14 16:22:22 UTC
Red Hat Issue Tracker   SAT-16325 0 None Migrated None 2024-06-06 16:10:20 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.