[projectaon] Re: Fwd: [jonblake 81157683] Followup regarding your site projectaon.org

  • From: Javier Fernandez-Sanguino <jfs@xxxxxxxxxxxx>
  • To: projectaon@xxxxxxxxxxxxx
  • Date: Tue, 12 Nov 2013 18:09:16 +0100

On 12 November 2013 01:05, Jack Van Zyl <jack.vanzyl@xxxxxxxxxxxxxxxxxx> wrote:
> Hi all,
>
> Holy crap. I’ve gone through the nginx error log on OpenShift for the Lone
> Wolf Adventures web app, and found the following. I hope it's because of the
> DreamHost server move, or some other reason, but FYI here's the details.
> According to Google Analytics (and that's if I've tagged the web app
> correctly) the web app averages 0 to 1 visitors per day (more like 0), and
> the site's only had 95 visits by 48 unique visitors. But looking at the
> server logs, something went on on 30/31 October (point 6 below):

Based on the logs you sent it might be good to review the application
to *not* bombard the host with requests when the service is down.

No idea how the web app works, but maybe, it could change the
interface when it detects several errors from "upstream" to tell the
users that the "service is down". It should only retry again after X
minutes have passed (with X increasing if the service is still down).

Accesing "Upstream" (i.e. projectaon.org) 3600 times / hour sounds too
much. And might be the source of the problem reported by Dreamhost.

> Point 6 makes me think there's some bot or something hitting
> lonewolfadventures.projectaon.org, and this app of course downloads the data
> and images from the main site. I really hope there's some other cause, but
> I'd be happy to switch the app off if that would be a good idea.

If you have a web app you are for sure getting hit by, at least Google
Bot (and probably more). Can you filter out bots access from the
application? Maybe adding a /robots.txt saying "Go away" would work.
(some bots, i.e. Google, honor it)

Since the Google Analytics engine doesn't trip (and that's JavaScript
code) its probably because the bots do not run JavaScript. So another
way to avoid them entirely is to have a JavaScript redirect in the
main page that access the *real* application. (i.e. users getting
http://lonewolfadventures.projectaon.org/ get redirected through
JavaScript to http://lonewolfadventures.projectaon.org/app.html). That
would also prevent bots from triggering the application.

Regards

Javier

~~~~~~
Manage your subscription at http://www.freelists.org/list/projectaon


Other related posts: