Upload to CDN does not set correct content-type for tar.gz files
Bug #1427889 reported by
Alice Chen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Trafodion |
Fix Released
|
High
|
Alice Chen | ||
Bug Description
Uploading *.tar.gz files to the CDN sets the incorrect content-type. This is causing the filename to be mangled on download.
Revision history for this message
| Alice Chen (alchen) wrote | #1 |
| Changed in trafodion: | |
| assignee: | nobody → Alice Chen (alchen) |
| status: | New → Fix Committed |
| Changed in trafodion: | |
| status: | Fix Committed → Fix Released |
| Changed in trafodion: | |
| milestone: | none → r1.0 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Trafodion Jenkins
Branch: master
commit 3d797939461a5c5
Author: Alice Chen <email address hidden>
Changed the algorithm so that files are individually uploaded.
This way they can be processed correctly. Apparently, Swift
also has a bug where you specifying the header content-type is
ignored during upload. To get around that problem we run a POST
command after uploading to make sure the headers we want are set.
Also changed /usr/local/
readable/writeable since we have user information in that file.
Due to that change jenkins needs to be given sudo access to that file.
Change-Id: If6ae68f306f28a