I just thought of one last component that I did not explain previously:
This JS is being called through a perl script:
<script language="JavaScript"
src="http://mydomain.com/my/perl/file.pl?param=value";
type="text/javascript">
</script>
So file.pl spits out "Content-type: text/JavaScript\n\n" followed by
some JavaScript.
I have simplified my test to show:
This does NOT give a request to the apache logs:
-----------------------------
function myFunction () {
var img_src =
"https://mydomain.com/images/ping.gif?n=1";;
var img = new Image();
img.src = img_src;
}
myFunction();
------------------------------
But this DOES:
------------------------------
function myFucntion () {
var img_src =
"https://mydomain.com/images/ping.gif?n=2";;
var conv_img = new Image();
conv_img.onload = function() {}
conv_img.src = img_src;
}
myFunction();
------------------------------
Again, i understand that this is a little off-topic.
Feel free to ignore, but if you can help explain this strange behavior
in IE7 I would be very grateful.
Thanks.
--Alex
On Nov 12, 2007 6:17 PM, Tom Metro <[EMAIL PROTECTED]> wrote:
> Alex Brelsfoard wrote:
> > Part of the img src does include a large random number.
> > On top of that I have also checked the temporary internet folder and I
> > see multiple copies (with different random numbers) of the same image
> > there.
>
> That would suggest it is working. At least from the browser's perspective.
>
>
> > I have run this test with a cleared cache, and with previous copies in
> > cache.
> > the results do not vary.
> > This makes no sense to me either.
>
> After you clear the cache, do you exit and restart the browser?
> (Insuring that the IE process actually terminated before restarting it?)
> It may be caching the file in memory. (You'd think clearing the cache
> would clear the memory too, but who knows, could be a bug in IE7.)
>
> The other option to consider is the involvement of a caching proxy. Is
> IE configured to use a proxy? Try running a packet sniffer to see where
> it is actually connecting. You might also be faced with a transparent
> caching proxy at an ISP, which you won't be able to bypass from the
> client side, but should have the same effect on all browsers running on
> the machine running IE7.
>
> One reason why you might see differences among browsers even if there is
> a transparent caching proxy is that the browsers might use different
> headers in the request. A packet sniffer would bring that to light.
>
> Have you explored setting the headers from the server side of things? If
> this is just a simple image bug used for tracking purposes, you could
> throw together a CGI with a few lines of code that sets the headers and
> returns the image. There are probably scripts already available that do
> this.
>
>
> -Tom
>
> --
> Tom Metro
> Venture Logic, Newton, MA, USA
> "Enterprise solutions through open source."
> Professional Profile: http://tmetro.venturelogic.com/
>
> _______________________________________________
> Boston-pm mailing list
> [email protected]
> http://mail.pm.org/mailman/listinfo/boston-pm
>
_______________________________________________
Boston-pm mailing list
[email protected]
http://mail.pm.org/mailman/listinfo/boston-pm
![https://mydomain.com/images/ping.gif?n=1"](https://mydomain.com/images/ping.gif?n=1"){kind=link}
![https://mydomain.com/images/ping.gif?n=2"](https://mydomain.com/images/ping.gif?n=2"){kind=link}