New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Send User-Agent as the monitor info #2154
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine to me, Cedric do you have issues with this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me too! Thanks @bbockelm !
Looks like this breaks HTTP transfers. I will need to revert and make another release. Here are excerpts from the logs without this change:
and then with this change:
@bbockelm Did you test locally the change when proposing the pull request? |
@bbockelm Could you look at this again and see why this is happening? |
@abh3 Cedric already created a pull request with a fix, which I confirmed and merged into |
Then whose problem was it and what was the problem?
…________________________________
From: Guilherme Amadio ***@***.***>
Sent: Wednesday, January 24, 2024 11:02 PM
To: xrootd/xrootd ***@***.***>
Cc: Andrew Hanushevsky ***@***.***>; Mention ***@***.***>
Subject: Re: [xrootd/xrootd] Send User-Agent as the monitor info (PR #2154)
@abh3<https://github.com/abh3> Cedric already created a pull request with a fix, which I confirmed and merged into devel.
—
Reply to this email directly, view it on GitHub<#2154 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAUIW573JBT5367JNQ3C74DYQH7QVAVCNFSM6AAAAABAXFRMNSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBZGQ3DMMJXHE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hi @abh3, Brian used the Bridge to set the user-agent for the transfer and did not handle that case in the callback that is ran once the bridge executed the command. This prevented the file |
The problem was introduced by this pull request, and after I found out it broke http transfers, Cedric looked at it and fixed it. Today I'm going to make another release (5.6.6) including the fix. |
Hi Guilherme,
So, clearly, he never tested the change, sigh. OK, negative points here which means he gets lower priority unless we are assured the submitted patch has been tested. Perhaps even requiring a description on how to test the change so we can verify (that's the extreme case).
Andy
…________________________________
From: Guilherme Amadio ***@***.***>
Sent: Thursday, January 25, 2024 12:23 AM
To: xrootd/xrootd ***@***.***>
Cc: Andrew Hanushevsky ***@***.***>; Mention ***@***.***>
Subject: Re: [xrootd/xrootd] Send User-Agent as the monitor info (PR #2154)
The problem was introduced by this pull request, and after I found out it broke http transfers, Cedric looked at it and fixed it. Today I'm going to make another release (5.6.6) including the fix.
—
Reply to this email directly, view it on GitHub<#2154 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAUIW57Q5XFWQPWYYYGVEBLYQIJBXAVCNFSM6AAAAABAXFRMNSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBZGY2DANBXGM>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
My plan is to expand as much as possible our test suite to cover the most common operations such that we catch problems with patches when the pull request is opened. In #2134, the problem was caught by the new CI, but not the old. I am working on adding tests with http(s) transfers and a few authentication methods for 5.7. |
After the initial login to the xrootd bridge (and after parsing the first request's headers), perform a
kXR_set
for the monitoring info. TheUser-Agent
header is sent as the info.This is only done for the first request of a connection. It is assumed that all subsequent connections belong to the same user agent.