When a client specifies Expect: 100-continue in the request headers, the server needs to reply with HTTP/1.1 100 Continue to allow the client to send the potentially bulky request body.

It appears that XrdHttp sends the following instead, breaking each client in a unique way:

HTTP/1.1 100
Connection: Keep-Alive
Content-Length: 0

Some report an error but actually the upload succeeds, some report an error and the upload fails, some hang, and some even work.

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

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1120?email_source=notifications\u0026email_token=AA7NRDQN3OBZPVFQ6XI76XDQ64JIPA5CNFSM4KJVQNP2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IHVOM4Q", "url": "https://github.com/xrootd/xrootd/issues/1120?email_source=notifications\u0026email_token=AA7NRDQN3OBZPVFQ6XI76XDQ64JIPA5CNFSM4KJVQNP2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IHVOM4Q", "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