You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The plugin to retrieve license information detected by Software Heritage uses the default PHP GuzzleHttp client user agent, which makes it harder than it should be to identify it.
I don't know if there's other uses of HTTP clients in Fossology, but it would be nice if Fossology identified itself as such when crawling external resources. An ideal user agent string would:
clearly identify itself as fossology
provide version information on the fossology instance
and, if possible, identify an admin contact for the fossology instance.
Thanks for considering,
Nicolas Dandrimont - Staff Engineer @ Software Heritage
How to reproduce
Unknown; This has been noticed on the receiving end of Fossology's crawling!
I have created PR #1837 which adds the User-Agent to the HTTP requests. Currently I have set it as "fossology/", example "fossology/3.9.0-rc2". Does this sounds helpful?
And for the server contact information, under Admin >> Customize, we have a field called "Support Email Address" which can be used here. But I am not sure if everyone will be okay to send this information. Therefore, I am keeping this open here for discussion.
Description
The plugin to retrieve license information detected by Software Heritage uses the default PHP GuzzleHttp client user agent, which makes it harder than it should be to identify it.
I don't know if there's other uses of HTTP clients in Fossology, but it would be nice if Fossology identified itself as such when crawling external resources. An ideal user agent string would:
Thanks for considering,
Nicolas Dandrimont - Staff Engineer @ Software Heritage
How to reproduce
Unknown; This has been noticed on the receiving end of Fossology's crawling!
Versions
Unknown, because of the issue being reported.
Logs
Any logs (if any) generated in
Remote web server logs
FOSSology logs
Not applicable
Apache logs
Not applicable
Job logs
Not applicable
The text was updated successfully, but these errors were encountered: