Date: Mon, 16 Dec 2019 08:42:11 -0800
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJKZSP3YDMMYWFCZM6XN4ATTGHEVBNHHCABYU5A@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3300/566141520@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3300@github.com>
References: <quicwg/base-drafts/issues/3300@github.com>
Subject: Re: [quicwg/base-drafts] Forwarding upstream error mid-body to
 downstream (#3300)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5df7b3e313984_43373ff4d5ecd95c181280";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/FG1i8HZ0U5qE05HFOF9-NH8ya4M>


----==_mimepart_5df7b3e313984_43373ff4d5ecd95c181280
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

If the TCP connection is closed with a reset, there's no guarantee how many bytes the intermediary has read from the kernel buffer before the reset is received, so I don't think the behavior is likely to be that different.

If there's an error at the HTTP layer, then I think there would commonly be a change in what the client sees, but that seems like a buggy backend, so I'm not sure it's worth attempting to deal with more gracefully?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3300#issuecomment-566141520
----==_mimepart_5df7b3e313984_43373ff4d5ecd95c181280
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>If the TCP connection is closed with a reset, there's no guarantee how many bytes the intermediary has read from the kernel buffer before the reset is received, so I don't think the behavior is likely to be that different.</p>
<p>If there's an error at the HTTP layer, then I think there would commonly be a change in what the client sees, but that seems like a buggy backend, so I'm not sure it's worth attempting to deal with more gracefully?</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/issues/3300?email_source=notifications&amp;email_token=AFTOJKZPGTA2SQKE7BTN54TQY6VWHA5CNFSM4J2HSDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG7KEUA#issuecomment-566141520">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK5Z6JQ5GQCMR2BERATQY6VWHANCNFSM4J2HSDBQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK75BP2K2CZGGJX6PBDQY6VWHA5CNFSM4J2HSDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG7KEUA.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/3300?email_source=notifications\u0026email_token=AFTOJKZPGTA2SQKE7BTN54TQY6VWHA5CNFSM4J2HSDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG7KEUA#issuecomment-566141520",
"url": "https://github.com/quicwg/base-drafts/issues/3300?email_source=notifications\u0026email_token=AFTOJKZPGTA2SQKE7BTN54TQY6VWHA5CNFSM4J2HSDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG7KEUA#issuecomment-566141520",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5df7b3e313984_43373ff4d5ecd95c181280--