Firefox 3.0.19 REFUSES to reload my ASP.NET web page

I working on upgrading my website from asp.net 1.1 to 2.0. I discovered that I had some table cells with the following attribute:

<td bgcolor="93cad9" ...

which wasn't displaying the background color.

So I changed my source to

<td bgcolor="#93cad9" ...

which will fix the problem. I know this because I can change it on the fly with Firebug.

But when I run my updated page, the background color isn't displayed and the page source still shows the hex code without the leading pound sign (#). I assumed this was a cache issue. So I
 - reloaded the page
 - Shift-reloaded the page
 - Ctrl-reloaded the page
 - Shift-Ctrl-reloaded the page (and Ctrl-Shift)
 - Cleared private data for the cache
 - rebooted the computer
 - changed the attribute from bgcolor to style="background-color: #93cad9;"

This page had an onbeforeunload confirmation message which I disabled and then tried reloading again. Still no luck.

Because this page has had cache problems in the past, I actually append a random number to the end of the query string to the page so it is less likely to be cached by the browser.

I am not using any page caching in the web site (unless it gets turned on by default during the asp.net conversion process).

Any suggestions as to what is going on here?

Thank you.

LVL 1
ZekeLAAsked:
Who is Participating?
 
IqAndreasCommented:
No offense in any way, but I tend to do silly mistakes like this all the time.

Are you CERTAIN your ASP page was saved correctly? If you open up the ASP page on the server (not via the website path, but manually opening up the file system on your server computer), does it show up with your new modifications?

Have you tried using a different browser?
0
 
IqAndreasCommented:
Do you have a link to the ASP Page so we can view it?

Perhaps there was an error saving the changes onto the server? Or as you said, maybe some sort of automatic server side cache is going on.

Have you tried using a different browser?
0
 
Nenad RajsicCommented:
you might be behind a proxy server. If you are the likelihood is that your proxy server is caching your files. check with your sys/network admin.
0
 
ZekeLAAuthor Commented:
This is all on my local development machine: Win XP sp3, IIS 5.1.
0
 
ZekeLAAuthor Commented:
I figured this out just before opening IgAndreas suggestion but you were right on the money. The page involved a datagrid and I had only added the # sign to the edittemplate. I didn't figure it out until I viewed source in IE. The problem with Firebug and IE developer toolbar, etc. is that they interpret and display the official value (#hexcode) rather than the source (hexcode). You get the points anyway.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.