Forum Moderators: open
I've used both IE and Firefox, same delay.
I've turned off Javascripting same delay.
If a run a trace or ping to webmasterworld it is fairly quick.
I very recently fully updated windows XP. I was behind be 3 minor updates. I updated the Sun Javascripting engine. I also updated to Firefox 1.0.6 (latest).
I just tried Netscape 7.2 same one minute delay.
I have a DSL connection and have visited many other websites with no issues.
I've had this problem at least three days.
This long delay only occurs with webmasterworld. I'm not going to preview this post I'm afraid it will take to long!
I used Live HTTP headers on Firefox and for each access to Webmaster world (that's not in the cache) I actually see no header activity for the entire one minute delay, them boom, the new page is rendered very quickly.
It must be something to do with making the connection to the server itself.
I used webmasterworld's IP address directly, same delay, I do get to the home page but only after a huge delay. I retried my trace and ping and they are timely.
I've had the large delay for a page to open and then another large delay before all the images are rendered.
If I try to load this URL (showcase.netins.net) directly I get a long delay as well. But ping and trace to the server itself are fine.
One thing I wanted to find out is, is anyone else having this problem. It appears no one else is having this problem (yet). I thought I might hear WW is experiencing problems of some kind, or a denial of service attack.
Apparently not. I have another machine and ISP I can try. This is taking up too much of our time.
Thanks for the help.
Mack.
Have you tried adding the WebmasterWorld IP address directly to your computer's "hosts" file? That would eliminate the DNS lookup, which might help if DNS problems are what is slowing your access.
A different isp should show that problem up.
I see in my research WW is using:
Cache-Control : max-age=0
pragma : no-cache
in it's HTTP response header. I'm not sure what this achieves. I believe "Cache-Control: private" achieves the goal of no caching by ISP's but still allows browsers to cache.
Is this a new configuration at WebmasterWorld? Please let me know, that way I can work with my ISP and at least explain what changed at WW. Again I have no problem with many, many, other websites. So this looks like a Cache-Control directive problem. I know on my websites I have also disabled ISP cachine using the control above in my response headers. I want to see all the hits to my web pages!
With MSN as my ISP (using 56K dialup), everything works great.
Again the delay is actually about a minute per page view, it's horrendous, through my usual ISP using DSL.
This does seem like some type of cache handshaking problem, so moderators again, please let me know if WW has just made a change in its HTTP response headers about 3 or 4 days ago.
Thanks for all the help,
Bob
Have you tried checking the traceroutes to the Westhost nameservers?
I've already put the IP's of WW and the image server in my hosts table and still have the problem, so I don't think a name server is my issue. A connection is made then there is a very large delay. I really don't feel like digging into packet sniffing.
Regarding "noboby else having the problem", one thing I've learned is there can be a long delay in the first person reporting a problem, and then there can be a delayed cascade of reports thereafter.
My ISP is of moderate size, but they aren't small, but it is possilble no other user of my ISP also accesses WW.
I'll persue this with my ISP, but guess what their going to say, "It's only WebmasterWorld; so it can't be our problem", and of course I'll remind them that things work fine through MSN dialup, and time will pass. They may be implementing caching on their end and have problems, but I haven't had problems with other BB's either, just WW.
Thanks,
Bob
I had the previous IP since 7/31 which possibly is when the problem started. My DSL modem already had the firewall disabled, so it couldn't have been that.
I don't know why the problem was only with Webmasterworld, I had visited many, many, other sites? Perhaps WW uses a larger than average packet at some point? (I've always wondered why WW doesn't use GZIP compression, at level 1 compression no "system" CPU penalty and 4X page download speed gains.)
I've run into Ethernet switches that, due to a failure, didn't repeat long packets on a single port, so who knows.
My ISP was supportive but was unable to duplicate the problem.
Again thanks for all the help and suggestions.
The only time I ever run into a problem is when I edit an existing post and then try and submit it. I always end up with hanging pages.
I'll try re-booting the modem as you did.
Try emptying out your stickymails if they've accumulated. I've been here 5 years, and that's just about always been the cause whenever I've experienced a slow-down.
I only had 8 messages total but deleting them made a world of difference. To bad cause a couple of them I wanted to keep.
Surprised this thread is still alive, and that someone else had the exact same symptoms!
Sorry, but I got nothing new to offer. WW's been running fine for me since the reset of my DSL modem.
When you reset did you get an new IP address? I'm sure I did.
It seems that after my initial 45 second wait there is a period of a minute or so that I can run all over the WW site rapidly then there is a big lag again.
The problem is still only WW related.
What did change at WW?
It seems if you have a large delay accessing WebmasterWorld make sure you get a new IP address from your ISP! Could be tough for some!
I wonder if Googlebot could possibly experience the same delay? Could be devastating to WW indexing at Google.
Could WW be selectively, and partially, blocking IP's?
It will be interesting to follow this saga.
> Could WW be selectively, and partially, blocking IP's?
nope - we ban em or not ban em via htaccess is it. If an ip is banned - you get an access denied msg.
I'll have to go back and rerun the solution that worked before after I rest up from the trip.
I spent an hour on the phone with ISP techs who are only 6 miles away and they tried a bunch of things with me. Webmasterworld loads fine in their office. They think that it might be slowed by some sort of filtering.
I have tried with and without firewalls, routers, and even tried on my Linux machine. Tracert doesn't seem to raise flags. I tried different browsers and deleted cash and cookies and started over.
I may be missing something obvious. The mess we are in down here with these two storms has me very distracted. When CNN sets up shop in your town it's rarely a good thing.
Try the tracert command as see if by chance there is some sort of delay via a router .. I recently had a very strange problem via my broadband ISP provider...
Also try "pinging" WW and see what comes back from your location..
I could not see a dedicated server (fixed IP number) that I work with ... one of my emails wouldn't work and I couldn't pull up Google News...
Turns out that when I ran a tracert to that IP number from my firewall ip .. there was a router that had developed a "recursive loop" and my request would stall..
I then set a support ticket with my ISP (and so did the hosting company where the box is located) ... and the problem was cleared up within the hour...
But I had no access for half a day...and was certainly concerned...fortunately...there are other folks looking at this same box (and associated domains) and they were not having any problems..
From my end WW is loading fast and reliably these days...though, on occassion, there will be some delay (5 - 10 seconds)...
I could not see a dedicated server (fixed IP number) that I work with ... one of my emails wouldn't work and I couldn't pull up Google News...
I have no other problems. The ping and tracert done yesterday from here and ISP show no problems.
I just don't know what to tell you. There is nothing that I can see wrong on our end. I don't even know where to start looking at something like this.
I understand completely. This probably just needs to go on the back burner till some time passes. We have so many communication problems in coastal Louisiana, and it may in some unknown way be aggravated by that. My Cingular cell phone works everywhere except within a five mile radius of home.
