Issue 1046 in modpagespeed: Fetches with remaining data to be read don't fail

[modpag...@googlecode.com]

Status: Accepted
Owner: jcrow...@google.com
Labels: Type-Defect Priority-Medium

New issue 1046 by jcrow...@google.com: Fetches with remaining data to be
read don't fail
https://code.google.com/p/modpagespeed/issues/detail?id=1046

Fetches using the serf fetcher (tested using CacheUrlAsyncFetcher) report
success when the content-length is longer than the length of the received
data.

Curl via the command line gives the helpful message
curl: (18) transfer closed with 950 bytes remaining to read

Our fetches should fail in this situation as well.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[modpag...@googlecode.com]

Updates:
Labels: -Priority-Medium Priority-Low

Comment #1 on issue 1046 by jcrow...@google.com: Fetches with remaining

data to be read don't fail
https://code.google.com/p/modpagespeed/issues/detail?id=1046

This involves dealing with chunked encoding as well, which content-length
will not equal transferred size every time.

bumping to low priority.

[modpag...@googlecode.com]

Comment #2 on issue 1046 by jcro...@google.com: Fetches with remaining

data to be read don't fail
https://code.google.com/p/modpagespeed/issues/detail?id=1046

this issue has been migrated to github:
https://github.com/pagespeed/mod_pagespeed/issues/1046