Files not versioning correctly

[Nevtep]

I'm seeing old versions of my js assets served from cloudfront and files in S3 don't have timestamps on their names anymore. S3 has the latest version thou cloudfront delivers old ones.

Any idea what could I be doing wrong? this is my config:

cdnOptions = { publicDir: path.join(dirname, 'public') , viewsDir: path.join(dirname, 'lib') , domain: process.env.CDNHOST , bucket: process.env.S3BUCKET , key: process.env.AWSKEY , secret: process.env.AWSSECRET , hostname: 'staging.farmshares.com' , port: 80 , ssl: false , production: false , logger: winston.info };

[niftylettuce]

any luck?

[niftylettuce]

@Nevtep let me know!

[Nevtep]

Nope... just re-enabled cdn doing some tests... I cleared S3 before doing that ad everything seems updated... did cloudfront changed the way to lookup cached versions? files uploaded still don't have timestamps on their names

[Nevtep]

Nick still no timestamp on files, old versions appearing on cloudfront, any info that would help you know what's wrong?

[Nevtep]

Ok so, the filename?cache=timestamp sintax is not working for me, cloudfront is not returning the correct assets, in lines 118/125 you call createTag with a filename that is commented out to have the timestamp and use this ?cache=timestamp sintax, in the process assets method lines 460 and 468 are commented out to not include the timestamp on the names.

Is there anything about cloudfront config I should be doing to serve files correctly? it's serving old file versions for some reason.

Thanks

[Nevtep]

Ok found it!

• Forward Query String: No (Improves Caching)

that should be YES since we are sending the cache timestamp on the query string

This is closed but you should update your documentation

[niftylettuce]

@Nevtep amazing find. you ROCK

[Nevtep]

@niftylettuce Thank you for this cool lib :)