Hi Nick,
I did, and it's unfortunate - feel free to file a bug - but it's still far
from clear that this should result in returning a 404 to the user.
I don't think this is a bug, but I believe that 404 response is simply
better and more obvious than 500 in this case and since Blobstore API is
still "experimental" and "you were eager to get my feedback so that you
could improve the API", I think it's good time to talk about this now ;)
Just take a look at competing solutions that work this way:
- S3 returns 404 for NoSuchBucket and NoSuchKey errors [1],
- Azure Blob Service returns 404 for ContainerNotFound and BlobNotFound
errors [2],
- nginx returns 404 when file pointed by "X-Accel-Redirect" doesn't exist.
[1]
http://docs.amazonwebservices.com/AmazonS3/latest/API/index.html?ErrorCodeList.html
[2] http://msdn.microsoft.com/en-us/library/dd179439.aspx
Best regards,
Piotr Sikora < [email protected] >
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
