Images Missing when loading ASP page

[Ed]

I first noticed this in my own app. Images would show up missing [red X]
randomly on IE 6.0.2800.1106 on Windows 2000 server.

I then was able to repro this problem on Microsoft's website!!! The page I
used was
http://www.microsoft.com/windows/ie/downloads/critical/ie6sp1/default.asp
After pressing [F5] to refresh the page six times, I noticed missing images
on the page.

This problem seems to be very reproducible. I coded a sample ASP page which
references the same images 10 times on the same page. Loaded in IE. Upon
pressing [F5] several times, the images will be identified as missing [red
X]. Refresh the page again, it's fine.....etc.

I'm up-todate with all latest MS patches. Has anyone else seen this
problem?

Is this an ASP problem or is it an IE6 bug?

 

[Ray at]

I'd be willing to bet it's an IE issue, not an IIS issue. Try loading the
page in another browser, if you have another one installed. I think that of
all the times I've been to Microsoft's site, I've only seen the red X like
once or maybe twice.

Ray at home

 

[Jeff Clark]

i have seen that. All i could gather was that IIS was doing too many <%%>.

Try doing just one image and see what happens

I'd be willing to bet it's an IE issue, not an IIS issue. Try loading the
page in another browser, if you have another one installed. I think that of
all the times I've been to Microsoft's site, I've only seen the red X like
once or maybe twice.

Ray at home

I first noticed this in my own app. Images would show up missing [red X]
randomly on IE 6.0.2800.1106 on Windows 2000 server.

I then was able to repro this problem on Microsoft's website!!! The

page

I
used was
http://www.microsoft.com/windows/ie/downloads/critical/ie6sp1/default.asp
After pressing [F5] to refresh the page six times, I noticed missing images
on the page.

This problem seems to be very reproducible. I coded a sample ASP page which
references the same images 10 times on the same page. Loaded in IE. Upon
pressing [F5] several times, the images will be identified as missing [red
X]. Refresh the page again, it's fine.....etc.

I'm up-todate with all latest MS patches. Has anyone else seen this
problem?

Is this an ASP problem or is it an IE6 bug?

 

[Ed]

UPDATE!

I found out that if the ASP page contains <SCRIPT>, images that are
references multiple times on the same page would become red X upon pressing
[F5] (refresh) for several times. If I were to remove the <SCRIPT> from the
ASP, the red X problem went away.

Looks like a caching bug in IE 6...

(I'm cross-posting this to the IE6 group and see what the experts think.)

i have seen that. All i could gather was that IIS was doing too many

Try doing just one image and see what happens

I'd be willing to bet it's an IE issue, not an IIS issue. Try loading the
page in another browser, if you have another one installed. I think

that

of
all the times I've been to Microsoft's site, I've only seen the red X like
once or maybe twice.

Ray at home

I first noticed this in my own app. Images would show up missing [red X]
randomly on IE 6.0.2800.1106 on Windows 2000 server.

I then was able to repro this problem on Microsoft's website!!! The

page

I
used was
http://www.microsoft.com/windows/ie/downloads/critical/ie6sp1/default.asp
After pressing [F5] to refresh the page six times, I noticed missing images
on the page.

This problem seems to be very reproducible. I coded a sample ASP page which
references the same images 10 times on the same page. Loaded in IE. Upon
pressing [F5] several times, the images will be identified as missing [red
X]. Refresh the page again, it's fine.....etc.

I'm up-todate with all latest MS patches. Has anyone else seen this
problem?

Is this an ASP problem or is it an IE6 bug?

 

[Phillip Windell]

The problem was you were mixing apples and oranges.

<SCRIPT> is for client side-script and runs in the browser, which is
not ASP.
ASP is server-side and runs on the server, and uses "<% %>" as
delimiters.

When you removed the <SCRIPT> tags it worked like it should, before
that it wouldn't have.


--

Phillip Windell [CCNA, MVP, MCP]
WAND-TV (ABC Affiliate)
www.wandtv.com

UPDATE!

I found out that if the ASP page contains <SCRIPT>, images that are
references multiple times on the same page would become red X upon pressing
[F5] (refresh) for several times. If I were to remove the <SCRIPT> from the
ASP, the red X problem went away.

Looks like a caching bug in IE 6...

(I'm cross-posting this to the IE6 group and see what the experts think.)

i have seen that. All i could gather was that IIS was doing too

many

Try doing just one image and see what happens

"Ray at <%=sLocation%>" <myfirstname at lane 34 . komm> wrote in message

loading

the

think

that

red X
like

once or maybe twice.

Ray at home

I first noticed this in my own app. Images would show up

missing [red
X]

randomly on IE 6.0.2800.1106 on Windows 2000 server.

I then was able to repro this problem on Microsoft's

website!!! The
page

I
used was

http://www.microsoft.com/windows/ie/downloads/critical/ie6sp1/default.
asp

After pressing [F5] to refresh the page six times, I noticed missing
images
on the page.

This problem seems to be very reproducible. I coded a sample ASP page
which
references the same images 10 times on the same page. Loaded

in IE.
Upon

pressing [F5] several times, the images will be identified as

missing
[red

X]. Refresh the page again, it's fine.....etc.

I'm up-todate with all latest MS patches. Has anyone else seen this
problem?

Is this an ASP problem or is it an IE6 bug?

 

[dlbjr]

What is this?

SCRIPT language="vbscript" runat="server">
Function f1()
f1 = "This is ASP"
End Function
</SCRIPT>
<SCRIPT language="javascript" runat="server">
function f2(){
return "This is ASP"
}
</SCRIPT>
<SCRIPT language="vbscript" runat="server">
With Response
.Write f1()
.Write "<BR/>"
.Write f2()
End With
</SCRIPT>

-dlbjr

Discerning resolutions for the alms

 

[Phillip Windell]

SCRIPT language="vbscript" runat="server">

Obviously that runs server-side when you add the "runat=" parameter,
but he never indicated he used it that way and I'm not going to assmue
he did that unless he says so. If he actually "showed the code" as we
always ask people to do, then we would already have known what way he
did it.