Fossil

Fix error conditions and exceptions when Transfer-Encoding chunked, partly from drh's Claude:

* Premature EOF was accepted as a valid EOF. * strtol --> strtoll with checking, to avoid casting errors * Per RFC 7230, match "chunked" at the end of the Transfer-Encoding value rather than a substring, so the word "chunked" appearing isn't acceped as a token * make nPrior unsigned int to match blob_size() to avoid a negative offset on large replies * Report only the chunk bytes actually received, not chunk bytes from the header, so the number is correct if the connection terminates part-way. (leaf check-in: 441a35ce2a ... user: danshearer tags: http1-1-chunked)

Some egress filters drop all HTTP version 1.0 traffic at the Web Application Firewalls (WAF). WAFs commonly provided by CDN (Content Distribution Networks) such as CloudFlare and AWS to their customers have such controls on them, and there are understandable policy reasons for disallowing 1.0. It is almost exclusively used by old software that is often exploitable (eg ancient versions of curl). Fossil users within virtual machines with such egress filters in place get confusing messages along the lines of "Upgrade required". This is inconvenient for Fossil users, and the quick solution is to seek a git mirror for the Fossil repo if one is available, because git just works.

There is no need to upgrade the Fossil server to support 1.1 to solve the egress problem.

This is (I believe) an RFC compliant minimal implementation and it seems to work, but none of the optional extensions are supported because I don't think Fossil needs them. It does need more careful checking on the supplied chunk length because strtol is insufficient. (check-in: 0f8a7d6095 ... user: danshearer tags: http1-1-chunked)