Replies not posting revisited.

F

Fuzz

Joined
Jun 8, 1999
Messages
33
It's definitely not my browser's cache.

I know because

a) I tried with another browser, same thing
b) I dialed into a different ISP and was able to see the thread properly, and
c) I was able to telnet into a UNIX shell account and access the thread I wanted using Lynx (that is, the UNIX box was getting the proper info from whatever Internet connection it has)

Which seems to point to some sort of caching going on either at my ISP or yours (mine being more likely) or, if those options weren't odious enough, there could be some sort of caching going on somewhere in the Microsoft TCP/IP stack at a layer below the browser somewhere. *Twilight Zone Theme*

I'll call the BellSouth.Net NOC tomorrow and ask if they're dinking around with some of those new Cisco Robin boxes.

Meanwhile, any thoughts?

Fuzz.

PS- The index page always seems to acknowledge the post. The number of posts goes up, the time that I posted is there, but no browser on my system can make that page load (Opera, Netscape, IE), even if I delete the cache by hand first.
 
The index page is cgi generated, and therefore cannot be cached, it's the HTML pages that would have the problems.

Call Bellsouth and findout if they are using a proxy server, and if so, how to get around it.

Spark

------------------
Kevin Jon Schlossberg
SysOp and Administrator for BladeForums.com

Insert witty quip here
 
It's not going to be a proxy server we're concerned about but rather a web-caching server. Like the new Cisco Robin boxes (we don't discuss the old, yucky web-caching servers Cisco used to sell...). The way to get around it is to have them disable caching for your IP address.

This is probably an issue that has already been covered in an RFC somewhere. There's probably some information you can include in the IP header to indicate time-sensitive non-cachable data. If not now then for IPv6
wink.gif


But now here's an interesting twist, in another browser window I have open right now (IE5), I can hit Refresh and get the updated thread. And then I can hit Refresh again and get the old thread. Hit it again and get the updated thread, hit it again...
This didn't happen before, before I would hit Refresh dozens of times before giving up.

Weird, but this could be some IE5 anomaly on top of the other issues.

Just thought I'd mention it.
 
As I feared, web-caching servers
frown.gif


I only got confirmation that they're using them for ADSL service.

I've requested that BladeForums (and every other UBB-based site I visit) not be cached, but I wasn't given a firm answer either way.
 
Find another ISP, and for god's sake, stay away from AOL. 99% of all UBB problems seem to be with AOL users, the other 1% being actual problems or operator headspace and timing.

If they are caching this, god knows what else they are caching.

Thanks for digging in and doing the research on this, I hope that it works out in the end.

Spark

------------------
Kevin Jon Schlossberg
SysOp and Administrator for BladeForums.com

Insert witty quip here
 
You must log in or register to reply here.
Back
Top