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 1958223 - Pages not displaying if default http proxy name has special characters
Summary: Pages not displaying if default http proxy name has special characters
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.9.0
Hardware: All
OS: All
high
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-07 13:46 UTC by Tasos Papaioannou
Modified: 2024-06-06 00:48 UTC (History)
3 users (show)

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

Attachments (Terms of Use)
Screenshot of Products page (30.21 KB, image/png)
2021-05-07 13:46 UTC, Tasos Papaioannou 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-25410 0 None Migrated None 2024-06-06 00:48:01 UTC

Description Tasos Papaioannou 2021-05-07 13:46:10 UTC 
Created attachment 1780747 [details]
Screenshot of Products page

Description of problem:

If a default HTTP Proxy has been set under Administer > Settings > Content > Default HTTP Proxy, and if the proxy name has certain special characters in it, then some pages do not display properly in the UI.

Example proxy names with this issue:

proxy'1
proxy"1
proxy\1

Proxy names without the issue:

proxy-1
proxy 1
proxy?~`1
proxy,<.>/?;:
proxy%@#$%^&*()_+=
proxy][}{|


Screenshot of the Content > Products page (on 6.9.2 snap 2.0) attached, showing that the products are not displayed.

Other pages with this problem include:

Content > Content Credentials
Content > Sync Plans
Hosts > Content Hosts


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

6.9.2

How reproducible:

100%

Steps to Reproduce:

See description above.

Actual results:

Pages don't display properly when default global content http proxy has single or double quotation marks or backslashes.

Expected results:

Pages display properly.

Additional info:
Comment 1 Tasos Papaioannou 2021-05-07 13:50:46 UTC 
Same issue exists in 6.8.6 as well.
Comment 4 Eric Helms 2024-06-06 00:48:03 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.