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.

Description of problem:
Per client: "I have a repo on my local network and I want to include it in Satellite. The problem is that in order to do that I must configure a squid. Can you please include an option to bypass the proxy configured in Satellite?"

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


How reproducible: 100% (on client's local network)


Steps to Reproduce:
1. Create a repository for a private repo on a local network
2. Attempt to synchronize without extra configuration
3. 

Actual results:
The client must configure a squid to allow the repository on his network to sync with Satellite.

Expected results:
The repository on his network will sync with Satellite by default with no extra configuration outside of Satellite needed.

Additional info:

*** This bug has been marked as a duplicate of bug 1132980 ***