Tim said:
I've just come across a Javascript tag that looks like this:
There is no such thing as a "Javascript tag". Perhaps you want to get the
basics right before you start second-guessing other developers?
<script type="text/javascript"
src="js/headerSelectUi.js?forcerefresh=0001" >
</script>
That is an (X)HTML `script' element, with a `type' attribute value of
"text/javascript".
Is there any possible reason for the argument at the end of the URL?
Yes, but it is no argument (no JS/ES method there), but a parameter (value).
The included *.js file never references "forcerefresh", and as far as
I know, it wouldn't be possible for it to.
It isn't. Client-side script code can only use the URI of the document that
it is included by, and perhaps the document that referred to the former, as
a referent.
Possible reasons include, in descending order of likelihood:
1. People who don't have a minimum clue (i.e., people who have either not
read or not understood [1]).
2. People who lack the opportunity or ability to reconfigure their Web
server according to [1] (i.e., people who should LART/switch their
Web hoster or get a minimum clue about their server).
3. People who have identified a broken Web cache that, despite proper cache
controlling headers, would provide the old resource when the parameter
was omitted, and are dependent on their application to work with that
cache. (I would be interested to know what Web cache that is.)
4. People who use the query parameter (not argument, here) to generate a
different version of the same original resource server-side.
PointedEars
___________
[1] <
http://www.mnot.net/cache_docs/>