httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 49786] Range header incorrectly handled when entitiy is not cached
Date Mon, 23 Aug 2010 20:37:49 GMT

Ryan Hope <> changed:

           What    |Removed                     |Added
                 CC|                            |

--- Comment #3 from Ryan Hope <> 2010-08-23 16:37:46 EDT ---
It looks like the fix in bug 49113 was to simply not cache partial
requests/responses.  While that fix does make sure that the client gets what
it's expecting, it also makes the caching mostly useless for an application
like ours where most of the requests are partial.

What I'd like to see is that a non-conditional request for a partial range is
actually translated into a non-conditional full request when it is proxied out
to the origin server (assumign it misses the cache), then the full response is
cached, but only the partial response is sent to the client.

Since full documents that are stored in the cache are handled correctly when
there's a partial request, it seems like it would be pretty straighforward (or
at least the fix would be similar to bug ID 44579) to just translate a partial
cache miss into a full request to the origin, then break it up into partial on
the response.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message