Hacker News new | ask | show | jobs
by nsgi 3906 days ago
It makes sense if there's an image with the word "ad" in the url. Probably something similar to that.
1 comments
derefr 3906 days ago
A bit frightening to think about: SHA hexdigests (as used in, e.g., cache-busting) can contain the two-character-sequence "ad".
link
userbinator 3906 days ago
I don't think adblockers will be so naive as to block anything that contains "ad" in the URL, but then again, there's a name for the bug caused by this particular type of matching:

https://en.wikipedia.org/wiki/Scunthorpe_problem

...so maybe some of them do have rather silly rulesets.

link
derefr 3905 days ago
They don't usually match on something as silly as the regexp /ad/, no—but they _do_ frequently contain a regexp like /\bad\b/.

The problem being—and this is painful personal experience speaking—web frameworks will frequently also cater to directory inode limits of caching reverse-proxies in their cache-busting code by doing something like this:

    "/#{sha[0..1]}/#{sha}.#{orig_ext}"
...which means that, for a SHA that starts with "ad", you get an "/ad/" in the URL.
link