Skip to content
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

XRootD HTTP erroneously returns old Digest header #1956

Closed
bbockelm opened this issue Mar 12, 2023 · 6 comments · Fixed by #1973
Closed

XRootD HTTP erroneously returns old Digest header #1956

bbockelm opened this issue Mar 12, 2023 · 6 comments · Fixed by #1973
Assignees
Milestone

Comments

@bbockelm
Copy link
Contributor

The variable holding the Digest response header, m_digest_header, is not reset between requests. This causes the digest header to be sent when the object is reused by a later request.

Note if the subsequent request sets the Want-Digest header, the stale header is not returned. Hence, it's only set when the client isn't expecting it.

@smithdh
Copy link
Contributor

smithdh commented Mar 13, 2023

hi @bbockelm . Shall I open a PR for this, or would you like to do that?

@smithdh
Copy link
Contributor

smithdh commented Mar 13, 2023

(And thank you for finding the problem)

@bbockelm
Copy link
Contributor Author

@smithdh - this fix got incorporated into the PR #1957 (see https://github.com/xrootd/xrootd/pull/1957/files#diff-56f7321e31ac4f62330e63a316d3c25360b99c453e09956a1730052d09c367ebR3020). Let's see if that one gets merged in a timely manner; otherwise, I'll send in the one-liner.

@smithdh
Copy link
Contributor

smithdh commented Mar 13, 2023

ah, that's great, thanks.

@xrootd-dev
Copy link

xrootd-dev commented Mar 14, 2023 via email

@amadio amadio added this to the 5.5.4 milestone Mar 17, 2023
@amadio
Copy link
Member

amadio commented Mar 20, 2023

@bbockelm Could you please split the fix for this issue into a separate pull request? I think that since #1957 is adding a new feature, and we'd like to apply the fix for this to XRootD 5.5.4, it's better to have just the fix for this as its own commit. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants