Alex Brelsfoard wrote: > This JS is being called through a perl script: > So file.pl spits out "Content-type: text/JavaScript\n\n" followed by > some JavaScript.
As long as your JS is executing, I don't expect that has an impact on the problem. > This does NOT give a request to the apache logs: > var img_src = "https://mydomain.com/images/ping.gif?n=1";; > > But this DOES: > var img_src = "https://mydomain.com/images/ping.gif?n=2";; You said you had code to add random data after the file name. I don't see that. > ...if you can help explain this strange behavior in IE7 I would be > very grateful. I reiterate the suggestions from my last posting: >> 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. [...] >> 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
![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}