Hmmm, I don't see the case where you get two responses: first is a continuation, the second is an error. The one here sent an error only. I will admit that the error code and message could be better.

My apologies. This issue is challenging to describe. For the request, there's two responses, but no payload. After the large (>1024) range request, this is the complete response:

HTTP/1.1 206 Partial Content
Connection: Keep-Alive
Server: XrootD/v5.5.4
Content-Length: 105417
Content-Type: multipart/byteranges; boundary=123456

HTTP/1.1 500 Internal Server Error
Connection: Close
Server: XrootD/v5.5.4
Content-Length: 24

Read vector is too long

I'd have expected the 206 reply to include a payload. And I suspect this behavior is confusing HTTP clients.

Since a ~~picture~~ pcap is worth a thousand words, I've attempted to attach a wireshark capture of the conversation.
red-xfer13-range-1025.pcapng.gz

And thank you for linking the related issues, Mason. I should have done a better search before opening this one. Please close this one if appropriate.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/2003#issuecomment-1529933725", "url": "https://github.com/xrootd/xrootd/issues/2003#issuecomment-1529933725", "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