views:

96

answers:

1

The Google Blobstore recently added support for serving partial byte ranges from a blob. When this method is invoked the response is generated with a HTTP 206 (Partial Content) status code. So it looks like app engine assumes that it is always serving a Range request in this case.

However, in my case I have bundled many files into one blob entry and I know the byte range of each. From the client's perspective they only access a URL representing an individual file. Behind the scenes, I invoke the ByteRange based serve method on the blob store to serve the file. HTTP 200 is the more appropriate response in my case however the app engine always returns 206.

Is there a way to override this behavior? (i.e. return 200 instead of 206?)

Thanks, Keyur

+1  A: 
nathan
I understand the caching implications and in fact that is why I was looking for a 200 here. As I mentioned, in my case the client is not making a range request. In this case the range seek into the blob is an implementation detail and not the contract between the client and the server.
Keyur
ahh apologies, I misread :)
nathan