- From: Jeffrey Yasskin <notifications@github.com>
- Date: Wed, 28 Nov 2018 12:05:25 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 28 November 2018 20:05:46 UTC
Browsers limit the length of URLs they'll fetch, but I haven't investigated exactly how. HTTP acknowledges these limits in https://tools.ietf.org/html/rfc7230#section-3.1.1 > Various ad hoc limitations on request-line length are found in > practice. It is RECOMMENDED that all HTTP senders and recipients > support, at a minimum, request-line lengths of 8000 octets. but doesn't say how they actually work. Even that acknowledgement is moving into the [HTTP/1.1-specific RFC](https://httpwg.org/http-core/draft-ietf-httpbis-messaging-latest.html#request.line) in the current HTTP update. This should be specified. I (weakly) think Fetch makes more sense than HTTP, since too-long URLs in requests will be rejected before they're sent to a server. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/841
Received on Wednesday, 28 November 2018 20:05:46 UTC