0

I have a known good web page that works without (known) errors when it loads. However, when I try to load it using a very laggy connection (more than 6-10 seconds to load the page - when all works well, it can load in under 500 ms), my hosting provider seems to generate 503 (too many requests) messages, and of course loading fails.

The page uses several modules I've written, and uses an asynchronous loader to read them once, when they're needed, so a single page load will often generate 10-20 GET requests for assorted resources. (Actually, it's closer to 60, but the rest come from a Google CDN, without error).

The hosting provider doesn't seem to understand (or, perhaps, care) about this problem, of course. I'm curious, though: does this sound like something that could be automatically generated by Apache (e.g. using mod_security or mod_cband), and would this be something that didn't show up on the log? I am very much a novice with Apache config, but find this error is forcing me to learn it.

Also, is there something I can do, either with my javascript or some setting on my website to force a retry if this happens?

2
Contributors
1
Reply
4
Views
2 Years
Discussion Span
Last Post by LesF
0

Can you combine the 10 to 20 GET requests into 1? If you can pass a list if ids and return for example a dictionary of results, it can often be much better to retrieve a large chunk of data in one go rather than adding the overhead of a call for each small piece of data.

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.