Amazon Web Services(Cloud Front) and Avatars

[robdog]

Quick question, and sorry if this is posted in the wrong forum. Anyways, I have recently switched from MaxCDN to Amazon Web Services. The one thing I did notice is that the query string is NOT taken into account for busting the cache on images. This is proving to be a problem when people update their avatars.

Is there a way to move the query string cache busting into the filename? Or has anyone figured out a way to get this to work properly?

Thanks.

 

[Paul B]

Avatars are appended with a date string, which changes ech time the avatar is uploaded.

This is mine for example: http://xenforo.com/community/data/avatars/l/0/521.jpg?1321091944

 

[robdog]

Avatars are appended with a date string, which changes ech time the avatar is uploaded.

This is mine for example: http://xenforo.com/community/data/avatars/l/0/521.jpg?1321091944

Yes, I see the query string being used as a "cache buster", but this is not supported by Amazon Web Services. (Cloud Front using the query string to bust the cache)

I was wondering if we could be the query string time stamp into the filename(ie: http://xenforo.com/community/data/avatars/l/0/521_1321091944.jpg)? Or if someone found a way to get the query string to work with AWS.

 

[Jake Bunce]

Amazon ignores the timestamp in the request? That's a booger.

Is there a way to move the query string cache busting into the filename?

Not without an addon or code modification.

 

[robdog]

Amazon ignores the timestamp in the request? That's a booger.

Yeah, I have a question in to them and seeing if they are going to support that anytime soon. Not sure what I am going to do if they come back with a NO, lol.

Not without an addon or code modification.

That is what I was afraid of.

 

[melbo]

Has anyone sorted this out? Having the same problem.
Members avatars are showing as different depending on the page display.

 

[taylor_smith]

We're preparing to move to Amazon Web Services, too. Really interested to find a solution.

 

[melbo]

I think I fixed it by telling my Distribution > Behaviors > Default > 'Forward Query Strings' > Yes
This seems to allow AWS to see the ? 12345678 date stamp behind the url. Within ~15 minutes, all of my problems cleared but I will closely monitor this to see if it introduces any other abnormalities.