Closed everetteallen closed 3 years ago
Can you check with the latest push? I've merged in some changes that address HTTP/2 responses.
@grahampugh That push seems to have fixed the issue. I now see response codes and correct behavior for uploading or not if existing package and the category is getting set as expected. Thanks!
Awesome!
So I am seeing mixed messages in a verbose run of the jamf-upload processor. Here is the confusing output:
Looks like the HTTP response is not being decoded properly but I can't tell for sure. The sanitized full output is below along with
/tmp/jamf_upload/curl_output_from_jamf_upload.txt
I am seeing this from 2 10.15.7 devices with Jamf Pro 10.27.0 and 10.28.0. The package does in fact upload and eventually become available. Also note that if I run the same command a second time it fails to detect that the package with the same name already exists. Thanks!Full -vv output from autopkg sanitized