Home/ Questions/Q 554937
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T11:45:47+00:00

I’m currently playing around with a build / deployment script for minifying static resources.

  • 0

I’m currently playing around with a build / deployment script for minifying static resources. Following good practice I’d like to set an expire header far into the future for most of my javascript, stylesheet and images.

To my question, when one or more of the static files has changed clients should ask for the newest version of the file. Will adding something like /css/style.css ?1235 after the url be enough to trigger a new request? Or do I have to rename all my static files for each build (something like /css/style _12345.css)?

Update: Just to clarify, the reason that I’m asking is that I’ve noticed that a lot of other deployment scripts seems to take the “hard” path by renaming each file.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    RFC 2616 3.2 Uniform Resource Identifiers says:

    As far as HTTP is concerned, Uniform Resource Identifiers are simply formatted strings which identify–via name, location, or any other characteristic–a resource.

    So, http://foo/bar is a different resource to http://foo/bar?baz.

    Some URIs are treated as equivalent, so http://foo/bar?baz is the same resource as http://foo/bar?BAZ (see 3.2.3 URI Comparison).

    HTTP does contain some caching exceptions for handling the query part (see 13.9 Side Effects of GET and HEAD). I understand these to only apply to the exact same query.

    • 0