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.

+++ This bug was initially created as a clone of Bug #1222707 +++

Description of problem:

I have multiple Source RPM repos that are synced but are only being published via https.

SRPMs are not downloadable using yum at the client (see also: Bug 1378442).

However, on the other hand, after fetching a huge stash of GBs of RHEL SRPM, it is just not useable.

There is no option in the UI to change the publish option to allow http.

In order to implement this functionality, I think the source code in Bug 1222707 is pretty much useable.

At this time, Red Hat repositories may only be published via HTTPS due to the subscription model and controls around making Red Hat content available.  In other words, this is working as designed.