Wedge

Public area => The Pub => Features => Topic started by: Arantor on November 11th, 2011, 02:23 PM

Title: Aeva caching headers
Post by: Arantor on November 11th, 2011, 02:23 PM

I'm not sure whether this is a bug or not, and I'll investigate properly later but wanted to record it for now.

Just had a case where a user uploaded a file to Aeva Media, I downloaded it, and subsequently (minutes later) the file was updated, but every time I hit the download, I was still getting the cached earlier download.

I'm not sure off hand what headers are sent but it seems we may have to use the cache control headers to validate the time of last update.

Title: Re: Aeva caching headers
Post by: Nao on November 11th, 2011, 03:06 PM

Well that'll be taken into account with the upcoming filename rewrite where the time will be specified.

Title: Re: Aeva caching headers
Post by: Dragooon on November 11th, 2011, 03:33 PM

I am not sure if AeMe/SMG was treating filename header properly, I don't think it provided proper 304/Not modified if not modified along with E-Tag and file modified times.

Title: Re: Aeva caching headers
Post by: Nao on November 11th, 2011, 08:42 PM

IIRC, originally you did it the wrong way and I didn't bother to check, and then you told me you'd noticed it was flawed so you fixed something etc etc... I don't know where we ended up in the end, but I remember I didn't spend a lot of time on this...