5 ms·
Yes, that's one of the method that was used: from https://news.ycombinator.com/item?id=9284226 https://news.ycombinator.com/item?id=9284226 : > The first roun
by madlag 12y ago
Yes, that's one of the method that was used:
from https://news.ycombinator.com/item?id=9284226 https://news.ycombinator.com/item?id=9284226 :
> The first round was cross-domain JavaScript, stopped with an "alert()". Second round was cross-domain <img>, stopped with referrer. Third was DDoS-ing GitHub Pages. Fourth is the ongoing TCP SYN Flood attack.
- hifier 12y agoIn that case, why is https://github.com/greatfire/ https://github.com/greatfire/ still returning the alert(..) js when not coming from Baidu?
- pyre 12y ago> > The first round was cross-domain JavaScript, stopped with an "alert()". > Second round was cross-domain <img>, stopped with referrer. It does not mention that the alert() used the referrer.
- hifier 12y agoApologies if I'm being dense, but is there some technical reason why it does not use the referrer to selectively block this traffic rather than blocking it for everyone?
- deleted 12y ago[deleted]
- pyre 12y agoThe content doesn't seem to be blocked if you remove the trailing slash. I don't really have an answer for you aside from that though. E.g.: - This works: https://github.com/greatfire https://github.com/greatfire - This doesn't: https://github.com/greatfire/ https://github.com/greatfire/ So far as I know, most links (external or internal) to a Github user's page do not use the trailing slash, so the effects would presumably be minimal.
- jurre 12y agoParsing the referrer would still require some work from their servers right?
- hifier 12y agoSure. I suppose that could be the reason. However, something like HA proxy[1] and (IIRC) CDNs like Akamai can be configured to inspect the headers and take various action. [1] http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#6 http://cbonte.github.io/haproxy-dconv/configuration-1.5.html...