Turns out that the main problem here (cached contents not being served up) is specific to udebs, and other content gets served up OK. There's a patch to that problem in #527188. However, I'm still not sure that giving a 304 if curl craps out is really the right answer here; I think it would be better to hand up a 50x to make it obvious that it's a server *problem*, rather than just some attempt at cache cleverness.
- Matt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
