Bug 1275010 - Hawkey does not provide version information in the user agent
Hawkey does not provide version information in the user agent
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: PackageKit (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Richard Hughes
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-24 17:19 EDT by Patrick Uiterwijk
Modified: 2015-10-27 07:39 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-10-27 07:39:40 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Patrick Uiterwijk 2015-10-24 17:19:27 EDT
Description of problem:
The entire user agent on HTTP requests performed by Hawkey is "PackageKit-Hawkey", which does not give any information for version.
It would be very useful if that information could be added.

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

How reproducible:
Persistent

Steps to Reproduce:
1. Make Hawkey perform an http request through PackageKit
2. Observe the web server's web log

Actual results:
User agent says "PackageKit-Hawkey"

Expected results:
User agent says something like "PackageKit-Hawkey/0.6.1"

Additional info:
Comment 1 Patrick Uiterwijk 2015-10-24 17:23:29 EDT
It would be even greater if information about the distribution running is provided.
Something like "PackageKit-Hawkey/0.6.1.fc22" would be the most ideal.
Comment 2 Richard Hughes 2015-10-27 07:39:40 EDT
commit ff2fe729ae2c864be5489f2ba260df18d9d9eb38
Author: Richard Hughes <richard@hughsie.com>
Date:   Tue Oct 27 11:39:11 2015 +0000

    Include the libhif version in the user agent string
    
    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1275010

Note You need to log in before you can comment on or make changes to this bug.