When FrontPage is trying to load an image from your site it creates a hit. So if you are actively developing with FrontPage it can create a lot of hits so the limit is triggered.
That’s also be added to why using FrontPage with remote images (especially here!) is a bad idea.
The site says I’m allowed 50,000 hits in 24 hours. Since my problem was that I wasn’t getting the images/photos to appear then there shouldn’t have been any hits until late yesterday when I finally found the problem. I would love to see the IP addresses of the hit count, sorted by IP address.
There are 11 guys in my fishing group. They rarely visit, only when I’ve updated it with a new fishing trip, which I haven’t done since last fall. All the old images/photos should be cached. There are a total of 3,241 files in the entire web. If each of us visited and requested every file in the site, putting the files in their cache, there would still be 14,349 hits left. Now if 16 people who had never been to my site, got the URL from this thread and visited, then yes, it would exceed the 50,000 allowance, if they visited every page in the site. I think someone was hammering the site but I can’t prove it. I can’t stop it.
I have never before hit the limit, developing several updated pages with photos and images in all of 2023. If I request an image/photo/page, it’s cached. I don’t think that counts as a hit if the page finds it in my cache. Even now, with a disabled site, I can still see most of the pages because they come from the cache, not the server. Only when I change / add a photo to the IF site will it be a hit.
Here’s the graph from my site. As you can see, it’s normally at about zero.
I believe every image is considered a hit, whether the response is 200 or 404.
If you have 999 images on every page, you will get 1000 hits for every page view.
Just 50 page views will cause your hosting account to be suspended
If my account is suspended then there shouldn’t be any hits right now. Yet I can see all the pages that are in my cache because the browser searches the cache first, before sending a file request to the web page. Only when I visit a page I haven’t seen since moving to IF do I get the ‘suspended’ page.
I’d like a technical person from IF to show me why a cached file counts as a hit since the file isn’t resolved by the web server.
Sometimes, a “cached” request still generates a hit without generating a download.
When I load the infinityfree.com main site, I see this:
The entire page is cached in my browser. But the very first page request is still an actual request (as you can tell by the non-zero request time), but the server responds with a “304 Not Modified” reply because the cached page is still valid.
All the CSS, JS and image files are fully cached and don’t cause any requests. But the cache check request is still a request.
As far as I know, the requests that are blocked by the browser validation system are not counted against your hits, so if the images don’t work, they shouldn’t be counted.
But the reality is that we don’t store the access logs for websites on free hosting. They are immediately aggregated into the hits counter and discarded. So I have no way to analyze the exact requests that caused this spike in traffic.
Can you see the IPs of the users accessing my page(s)? Is there one that has an extremely large number of hits for the previous 2 days?
Other than the queries about the problem that I was having there just shouldn’t be that many hits.
No. Like I said:
The only information we have is the information you see: a hit counter per day for the entire account. No exact times, no IP addresses and no specific domains or URLs.
Within 2 minutes of my account being reactivated it was again suspended for reaching the maximum number of hits. THIS IS NOT ME.
that would be 400+ requests per sec
I doubt that you were attacked by a botnet and it is probably a bug in the system
It’s not, it’s a permanent suspension, not a temporary one, because of extremely high traffic. This is also what you were told in the ticket you submitted.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
