Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1749317

Summary: Wrong Content-Type header value on HEAD and GET manifest requests
Product: Red Hat Satellite Reporter: Stefan Junker <sjunker>
Component: Container Management - ContentAssignee: Partha Aji <paji>
Status: CLOSED WONTFIX QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.5.0CC: apatel
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-01-19 21:34: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:

Description Stefan Junker 2019-09-05 11:08:44 UTC 
Description of problem:
Our test Satellite instance returns the wrong Content-Type.

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

How reproducible:
Always

Steps to Reproduce:
```
$ curl --head \
  -H "Authorization: Bearer b**************************************0" \
  -L https://sat-r220-02.lab.eng.rdu2.redhat.com/v2/default_organization-custom-ocp/manifests/4.0.0-0
HTTP/1.1 200 OK
Date: Thu, 05 Sep 2019 10:51:06 GMT
Server: Apache/2.4.6 (Red Hat Enterprise Linux)
Foreman_version: 1.20.1.35
Foreman_api_version: 2
Docker-Content-Digest: sha256:59c38273d9331211a5ad2c6fd10634f6db1932c15412e86bbeeba548c9c4c82c
Docker-Distribution-API-Version: registry/2.0
Cache-Control: max-age=0, private, must-revalidate
X-Request-Id: e388922a-f3f1-4f37-a9e9-a051cbc4a14f
X-Runtime: 0.147121
Strict-Transport-Security: max-age=0; includeSubdomains
X-Frame-Options: sameorigin
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
X-Download-Options: noopen
X-Permitted-Cross-Domain-Policies: none
Content-Security-Policy: default-src 'self'; child-src 'self'; connect-src 'self' ws: wss:; img-src 'self' data: *.gravatar.com; script-src 'unsafe-eval' 'unsafe-inline' 'self'; style-src 'unsafe-inline' 'self'
X-Powered-By: Phusion Passenger 4.0.18
Set-Cookie: request_method=HEAD; path=/; secure; HttpOnly; SameSite=Lax
Set-Cookie: _session_id=de7e74515301fffe0965ab3f0fefbc0d; path=/; secure; HttpOnly; SameSite=Lax
ETag: W/"59c38273d9331211a5ad2c6fd10634f6"
Status: 200 OK
Content-Type: application/json; charset=utf-8
```

I have also tried adding `-H "Accept: application/vnd.docker.distribution.manifest.v1+prettyjws"` to the call, which doesn't make a difference. 


Actual results:
Content-Type contains "application/json". 

Expected results:
Content-Type contains "application/vnd.docker.distribution.manifest.v1+prettyjws"


Additional info:
* BZ 1676626 is not an accurate duplicate of this, as that seems related to the endpoint at port TCP/5000 on the satellite address, wheres this ticket is using port TCP/443.
Comment 3 Stefan Junker 2019-09-05 11:34:36 UTC 
*** Bug 1746905 has been marked as a duplicate of this bug. ***
Comment 4 Mike McCune 2020-12-09 22:17:53 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in approximately a month. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 5 Mike McCune 2021-01-19 21:27:11 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact your Red Hat Account Team. Thank you.