Get a "500 read timeout" on this site.

see: http://www.telegraaf.nl/
See this with Google Chrome, some trouble with their server creating a container.

Anyone something on this?

There were issues on the site here: https://urlquery.net/report.php?id=6311629
IDS: http_inspect: JAVASCRIPT WHITESPACES EXCEEDS MAX ALLOWED → http://webcache.googleusercontent.com/search?q=cache:mGw-zxxx-LMJ:www.snort.org/search/sid/120-10+&cd=1&hl=nl&ct=clnk&gl=nl

Several other IDS alerts on site recently: https://urlquery.net/report.php?id=5866476

code hick-up:
[nothing detected] (script) a.ligatus dot com/?ids=45963&t=js
status: (referer=wXw.telegraaf.nl/)saved 957 bytes d4b9d464837a96a0e05e5b8cfdb42bd3f157a5dd
info: [decodingLevel=0] found JavaScript
suspicious:
from community.tcdn.nl/data/files/js/ ( get a 404 error,

polonus

Some AVG users reported malware: http://www.avgthreatlabs.com/website-safety-reports/domain/telegraaf.nl/

This was for IDS alerts for anomalous network traffic, but some of the snort alerts might come as questionable.
What I reported has to do with the server side of things, server management so to say.

polonus