Hi,
It was observed recently that while checksumming a large file (O(50GB)) during webdav TPC transfer via FTS. FTS reached an (internal) timeout which caused the transfers to fail. While the FTS timeout has since been understood and resolved, it raised a question on supporting 100-continue for a checksum request.
My current understanding is that XRootD supports the Expect 100 Continue header in the dedicated scenario:

When the http front-end is filling a buffer in the presence of read segmentation and the header was present, it will send a keepalive.

It was proposed (and hence this issue), that extending this functionality to Checksum requests would be a useful operation to support; so I'm following up here, as suggested.

Kind regards,
James


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/1857@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1857", "url": "https://github.com/xrootd/xrootd/issues/1857", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1